Vista SP1 Installations Deployed Using Operating System Deployment Cannot Hibernate

BlogMS Weekly Articles Published – 30th March to 5th April

BlogMS - Official Microsoft Team Blogs — Mon, 06 Apr 2009 12:42:27 GMT

237 Microsoft Team blogs searched, 115 blogs have new articles in the past 7 days. 327 new articles found

Solution: Vista SP1 Installations Deployed Using Operating System Deployment Cannot Hibernate

The Configuration Manager Support Team Blog — Tue, 07 Apr 2009 16:32:08 GMT

The folks over on the Configuration Manager team blog have a great post on how to resolve an issue we’re

Solution: Vista SP1 Installations Deployed Using Operating System Deployment Cannot Hibernate

Rod Trent at myITforum.com — Wed, 08 Apr 2009 23:34:58 GMT

Feed: The Configuration Manager Support Team Blog Posted on: Tuesday, April 07, 2009 9:32 AM Author:

re: Vista SP1 Installations Deployed Using Operating System Deployment Cannot Hibernate

Alex Nation — Wed, 29 Apr 2009 03:17:53 GMT

Would there be any positives using this method over simply running the cmd:

bcdedit.exe /create {resumeloadersettings} /d "Resume Loader Settings"

with a "Run Command Line" task?

re: Vista SP1 Installations Deployed Using Operating System Deployment Cannot Hibernate

Ramon Martinez — Thu, 21 May 2009 17:43:00 GMT

I have the same concern if using BCEDIT command line would be sufficient. I have already deployed this command line to all Vista laptops and now, I am wondering if the fix provided here is actually the fix? Please post your recommendation.

re: Vista SP1 Installations Deployed Using Operating System Deployment Cannot Hibernate

Luciferous — Fri, 21 Aug 2009 23:35:23 GMT

I imagine the concern in using the bcdedit command line over the above is, "what if the entry already exists"? We've got this pretty consistently in our environment too, right now. In fact, I was just about to implement the BCDEdit command as a "run command line" myself. Now I'm re-thinking it. I assume the thought is that, at some point in the future, a patch or service pack will fix the issue and you'll end up with (at best) two BCD entries or (at worst) a broken OSD process.