I am currently running SCCM 2007 SP2 R2 on a HP ProLiant DL380G5 server. For 3 or so months I have no ran into any issues with it and it has been a great product. Suddenly today after I was updating some software in packages clients started to slow down in a ridiculous fashion when attempting to image them from the PXE server. They'd boot into the boot image just fine, but once they came to the password protect screen and you enter the password, they'd start retrieving policy as normal, but it would take 3-4 minutes to do so, which is highly unusual. Then once my task sequence list came up I'd select one, and it would run extremely slow while trying to resolve dependencies, and later fail, not with a dependency failure, but just a simple hex code, which I searched and could only come up with Windows Updates errors. I ensured that all packages were updated on the distribution points, and have even removed the packages from the server and their links from the task sequences, and still the server is running beyond slow. Any ideas? I need to solve this ASAP as we have quite a few machines that need to be imaged soon. The alternative is to re-build the server, which I didn't originally setup except for the OS Deployment part. This is a last resort though as it would take 16-24 hours to properly rebuild our server as we have 23 different task sequences all with different sets of software. Any help is highly appreciated.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
I am currently running SCCM 2007 SP2 R2 on a HP ProLiant DL380G5 server. For 3 or so months I have no ran into any issues with it and it has been a great product. Suddenly today after I was updating some software in packages clients started to slow down in a ridiculous fashion when attempting to image them from the PXE server. They'd boot into the boot image just fine, but once they came to the password protect screen and you enter the password, they'd start retrieving policy as normal, but it would take 3-4 minutes to do so, which is highly unusual. Then once my task sequence list came up I'd select one, and it would run extremely slow while trying to resolve dependencies, and later fail, not with a dependency failure, but just a simple hex code, which I searched and could only come up with Windows Updates errors. I ensured that all packages were updated on the distribution points, and have even removed the packages from the server and their links from the task sequences, and still the server is running beyond slow. Any ideas? I need to solve this ASAP as we have quite a few machines that need to be imaged soon. The alternative is to re-build the server, which I didn't originally setup except for the OS Deployment part. This is a last resort though as it would take 16-24 hours to properly rebuild our server as we have 23 different task sequences all with different sets of software. Any help is highly appreciated.
Share this post
Link to post
Share on other sites