Thanks Acronis 11 Team, for such a shoddy product!
What a fantastic product. Upgrading from 10 to 11 completely cut off network communication to one of my offsite SBS servers and after a reboot no account can login. Every account gets stuck at "Applying Computer Settings".
This just keeps getting better and better! 160 Licenses later, I really think we may be looking for a new imaging solution. I have about 15 estimates I need to change.
I'd ask tech support but everyone who posts here knows how effective that is!
What a fantastic product. Upgrading from 10 to 11 completely cut off network communication to one of my offsite SBS servers and after a reboot no account can login. Every account gets stuck at "Applying Computer Settings".
This just keeps getting better and better! 160 Licenses later, I really think we may be looking for a new imaging solution. I have about 15 estimates I need to change.
I'd ask tech support but everyone who posts here knows how effective that is!
I had the same problem.
This helped me solve it:
h**p://www.sbsfaq.com/?p=1409
2. I initially installed some drivers manually. After reboot, the server stayed for ever on “Applying computer settings”, never showing he loggon screen. Restarting in Safe was OK. Starting using the Last Known Good Configuration fixed the problem. I then ran the HP Smart Update Manager which installed all the drivers required for this server.
3. There was left over information in the registry about the previous NICs. Tryied to clean up the registry but the “Connect to the Internet” wizard did not work properly. This took 5 hours as I did not know how to fix it. At the end someone on the http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/ forum pointed me in the right direction. The solution was:
Open a command prompt with Run as an Administrator,
type: SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
then type: devmgmt.msc
In the View menu, choose Show Hidden Devices
Now you are able to see the not present devices and can uninstall or remove them
As well as the above, consider this Microsoft article as well:
h**p://support.microsoft.com/kb/2004121
The problems described in the symptoms section occur because of a lock on the Service Control Manager (SCM) database. As a result of the lock, none of the services can access the SCM database to initialize their service start requests. To verify that a Windows computer is affected by the problem discussed in this article, run the following command from the command Prompt:
sc querylock
The output below would indicate that the SCM database is locked:
QueryServiceLockstatus - Success
IsLocked : True
LockOwner : .\NT Service Control Manager
LockDuration : 1090 (seconds since acquired)
Let me fix it myself
you can modify the behavior of HTTP.SYS to depend on another service being started first. To do this, perform the following steps:
Open Registry Editor
Navigate to HKLM\SYSTEM\CurrentControlSet\Services\HTTP and create the following Multi-string value: DependOnService
Double click the new DependOnService entry
Type CRYPTSVC in the Value Data field and click OK.
Reboot the server
NOTE: Please ensure that you make a backup of the registry / affected keys before making any changes to your system.