Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, December 14, 2012 5:04 PM
I am currently experiancing an issue which seems to be isolated to our Server 2008 SP1 servers running Blackberry Management, hosted on VMWare as virtuals.
It appears that application of GPO's kicks off 8 powershell processes that do not terminate. They continue to accumulate until the server runs out of memory and must be cycled to clear these powershell instances.
The 8 powershell instances that kick off repeatedly are:
Provider "WSMan" is Started.
Provider "Alias" is Started.
Provider "Environment" is Started.
Provider "FileSystem" is Started.
Provider "Function" is Started.
Provider "Registry" is Started.
Provider "Variable" is Started.
Provider "Certificate" is Started.
For troubleshooting, I had stopped SCOM management on the servers, this still occurred. For each server that I moved to an OU where only our "base domain" GPO applies, this appears to have stopped. It had previously been kicking off (and accumulating ps instances) every hour, on the hour. Once I removed one of the servers from having GPOs applied with the exception noted above, it ran once more after 6 hours, then once after 8 hours and has not run again for 36 hours.
Looking back through the powershell log, it seems these 8 processes used to run once per day, then they stopped running completely for about 20 days, then started to run once per hour for the next several months. The processes seem to be normal ps instances that run in the backround for events such as registry changes, etc. But for some reason now, they are not terminating.
Known bug? I cannot find any information on this.
Thanks in advance....
All replies (4)
Friday, December 14, 2012 5:06 PM
Have you looked at your scheduled tasks on that server?
[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "
Monday, December 17, 2012 3:08 AM
The 8 powershell instances that kick off repeatedly are:
Provider "WSMan" is Started.
Provider "Alias" is Started.
Provider "Environment" is Started.
Provider "FileSystem" is Started.
Provider "Function" is Started.
Provider "Registry" is Started.
Provider "Variable" is Started.
Provider "Certificate" is Started.
Just for the sake of clarification, this is just one instance of PowerShell starting. But as you mentioned, you will see this repeated for each instance of PowerShell that has started up.
For your issue, have you looked at using rsop.msc to look at your GPOs and see what startup scripts you have running? If any of those are PowerShell related, you can then go out to where the scripts are stored and troubleshoot those.
Boe Prox
Blog | PoshWSUS | PoshPAIG | PoshChat
Monday, December 17, 2012 10:20 AM
Also,
It may help to check you have NOT set the -noexit parameter on the task scheduler,
Regards,
Bertand1
Bertand1 Answered your Question? - Mark it as the Answer Been helpful rather than hindering? - Mark it as helpful!
Tuesday, December 18, 2012 6:21 AM
Hi,
Just checking in to see if the suggestions were helpful. Please let us know if you would like further assistance.
If you have any feedback on our support, please click here .
Cataleya Li
TechNet Community Support