You might want to enable both user environment and windows installer logging to get more information about what is going on:
221833 - How to enable user environment debug logging in retail builds of Windows http://support.microsoft.com/?kbid=221833
223300 - How to Enable Windows Installer Logging http://support.microsoft.com/?kbid=223300
_________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net ___ please respond in newsgroup, NOT by private email ___
"W.a.Sdanou" <wasdanou[ at ]gmail.com> wrote on 27 dec 2008 in microsoft.public.windows.terminal_services:
[Quoted Text] > Since a few month's were having a problem with installing new > software on both windows 2003 SP2 R2 terminal servers. We don't > know exactly when it occured first. No other servers seem to > have this problem. We tried to trace it back to some other > installed piece of software or windows update, but without any > succes. What happens is the following. When installing a small > piece of software like delprof.exe, it takes about 25 minutes > before it's done. During this time, msiexec.exe takes 25% of the > processor capacity. On other servers it takes about 10 seconds > to install. Its on a dual processor 3Ghz (with hyperthreading) > ProLiant DL360 G4p. Also, at times it takes a few minutes for > users to logon. this times it's the userinit.exe that uses 25% > processor capacity.Installing Windows updates or other software > takes hours. > > We have check about all the obviouse things, like slow hardware, > profiles, redirecting, other software but nothing came up. > > Does anyone have a suggestion, or had to cope with the same > problem?
|