When running the SMS Admin console locally on your administrative workstation, the CD generated may be different from one generated on the SMS Server.
Depending on your configuration you may receive the error; "unable to load sql server oledb..."
Cause:
The files used to generate the CD locally typically reside in C:\SMSAdmin\OSD
Resolution:
Make sure that the files in your local C:\SMSAdmin\OSD directory have been syncronised with those on the SMS server, [SMSInstallDirectory]\OSD.
Of particular note are the osdshell.exe and OSDWinPE.wim files.
The OSDWinPE.wim contains the customised background that you specified in the Windows PE tab of the MS Deployment workbench.
Blog Index
-
▼
2008
(40)
-
▼
April
(24)
- Access a Network Resource Alias using Computer Acc...
- ZTI DefaultDomainName setting lost
- ZTITattoo.wsf - OSD clears TaskSequence registry e...
- PowerShell appears to "hang" when executed from a ...
- Need to move the Microsoft Deployment Distribution...
- Fix Broken Windows Scripting Host
- Set Location in "Regional and Language Options" co...
- Dial up connections do not use LAN proxy settings
- Ever needed an Automated RunAs?
- LTI deployment fails with error "A connection to t...
- ZTI PreInstall phase fails with error 214700057
- ZTI Package update leaves .$M$ file(s)
- Error creating ZTI CD when using local SMS Console
- Various WMIC commands
- Various DSQUERY commands
- Using ImageX to compress a WIM file after modifica...
- When installing Windows XP on ESX you may receive ...
- VMWare Workstation - After WinPE deploy of sysprep...
- Pre-Stage Computer resource record in SMS
- Windows Path issues may prevent Group Policy from ...
- Hiding or Displaying Default Desktop icons
- ImportGPO.wsf may not import GPO's using a Migrati...
- Permissions for Moving a Computer Account
- Cached logons are available by default on a domain...
-
▼
April
(24)
Thursday, April 17, 2008
Error creating ZTI CD when using local SMS Console
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment