Currently I'm working on automating the provisioning of SCCM environments.
One of the things that came along was exporting and importing Task Sequences between SCCM environments.
After automatically dealing with the package references I was ready to import them in the target SCCM deployment with my script.
Sadly, this didn't work. Even with the ConfigMgr Console it didn't work. As I was not presented with some kind of error, I searched the Event Viewer.
There I found multiple APPCRASH events (eventid 1000) on wmiprvse.exe.
So there had to be something in the Task Sequence export files that causes WMI to crash.
Many times WMI crashes because of bad queries or non-existing WMI classes, or ..... yep memory issues.
After (manually :'( ) comparing the two SCCM deployments, I found out I was missing the Microsoft Deployment Toolkit 2010 Task Sequence steps on the target SCCM deployment. After installing that, all issues were gone.
It would be nice though if the ConfigMgr console could present me with a simple error, stating that MDT was missing. Arghh.....
Tuesday, August 9, 2011
Subscribe to:
Post Comments (Atom)
0 reacties:
Post a Comment