Hello, thanks for answers.
When was started update for SEP clients with new version, computers are restarted.
Old installation package (12.1.1101) is removed from SEP approximately 2 weeks, before is starting update until 12.1.2015.
Free disk space on C should be more than 1.5 GB.
It is not possible to start the update directly from SEPM because it would overload the network to a particular office, or you need to set up a large renovation period >1 month. Hope you find the problem faster. In this way, I started update to others office directly from SEPM (~10 computers) and not have any problems.
In following folders (win7) C:\ProgramData\Symantec\Symantec Endpoint Protection\12.1.1101.401.105\Data\Install\Logs\ contain SIS_INST.LOG with creation date 11.05.2012, i.e. log file with previous updates before version 12.1.1101. C:\Windows\Temp\ contains SEP_INST.LOG from 05.11.2011 -> log file since before two versions. The same situation with winXP : C:\Documents and Settings\All Users\Application Data\Symantec\Symantec Endpoint Protection\12.1.1101.401.105\Data\Install\Logs contains SIS_INST.LOG with creation date 21.06.2012, and C:\Windows\Temp\SEP_INST.LOG with creation date 21.06.2012. Several computers are checked from different group providers – there are missing a new log files. In same time file SIS_INST.LOG is locked from an application (can’t be deleted or renamed). The same situation with 4-5 computers checked from different group providers and different OS (win7 and winXP).
I ran some tests: a new SEPM package was created, for one group update was stopped on SEPM, a new package was placed for corresponding group provider and run an updates again. The problem computers, began to continuously download a new generated package (setup.exe).
What other can I check?