Well it looks like I no longer have to answer the question "when will Microsoft Deployment be released?" with the response "sometime soon :)".
Microsoft Deployment is now released!!
I wont go into all the details of what MDT does, you will find that information in many blogs (including my previous and future posts) and within the MDT documentation itself. Instead I would simply congratulate the development team for producing a worthy successor to BDD.
If you want to download MDT then you will find it here.
PingBack from http://www.leadfollowmove.com/archives/deployment/mdt-update
Updating from BDD2007 to MD did not work.
It seems as if the Database Schema has been changed - No Client was listed after upgading.
Even after setting up a new database and applying the necessary modifications i wasnt able to install a client.
Hopefully MD dint change my Database so i can go back to BDD...
There have been no database schema changes between BDD 2007 and MDT.
The issue must be caused by something else :).
it's not really related to this entry, but that's your latest one.
So, I'm deploying a Vista image by SMS OSD, the problem I have is that the junction point C:\Documents and Settings points to X:\Users and that's causing application issues.
I guess OSD is mounting the disk volume to X: while restoring the image.
I checked the documentations but haven't really seen it mentioned anywhere as a possible issue. Am I doing something wrong here, or is this the expected behavior?
Currently I do a workaround by deleting the junction point and recreating it with linkd.exe.
Any better ideas?
Junction points is a know issue. Here is a batch file that I use to fix the issue:
rd "Documents and Settings"
mklink /J "Documents and Settings" C:\Users
icacls "Documents and Settings" /deny Everyone:(RD)
rd "Application Data"
mklink /J "Application Data" C:\ProgramData
icacls "Application Data" /deny Everyone:(RD)
mklink /J "Desktop" C:\Users\Public\Desktop
mklink /J "Documents" C:\Users\Public\Documents
mklink /J "Favorites" C:\Users\Public\Favorites
rd "Start Menu"
mklink /J "Start Menu" "C:\ProgramData\Microsoft\Windows\Start Menu"
mklink /J "Templates" C:\ProgramData\Microsoft\Windows\Templates
rd "All Users"
mklink /D "All Users" C:\ProgramData
rd "Default User"
mklink /J "Default User" C:\Users\Default
mklink /J "Application Data" C:\Users\Default\AppData\Roaming
mklink /J Cookies C:\Users\Default\AppData\Roaming\Microsoft\Windows\Cookies
rd "Local Settings"
mklink /J "local Settings" C:\Users\Default\AppData\Local
icacls "local Settings" /deny Everyone:(RD)
rd "My Documents"
mklink /J "My Documents" C:\Users\Default\Documents
mklink /J NetHood "C:\Users\Default\AppData\Roaming\Microsoft\Windows\Network Shortcuts"
mklink /J PrintHood "C:\Users\Default\AppData\Roaming\Microsoft\Windows\Printer Shortcuts"
mklink /J Recent C:\Users\Default\AppData\Roaming\Microsoft\Windows\Recent
mklink /J SendTo C:\Users\Default\AppData\Roaming\Microsoft\Windows\SendTo
mklink /J "Start Menu" "C:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu"
mklink /J Templates C:\Users\Default\AppData\Roaming\Microsoft\Windows\Templates
mklink /J "Application Data" C:\Users\Default\AppData\Local
mklink /J History C:\Users\Default\AppData\Local\Microsoft\Windows\History
rd "Temporary Internet Files"
mklink /J "Temporary Internet Files" "C:\Users\Default\AppData\Local\Microsoft\Windows\Temporary Internet Files"
rd "My Music"
mklink /J "My Music" C:\Users\Default\Music
rd "My Pictures"
mklink /J "My Pictures" C:\Users\Default\Pictures
rd "My Videos"
mklink /J "My Videos" C:\Users\Default\Videos
mklink /J "My Music" C:\Users\Public\Music
mklink /J "My Pictures" C:\Users\Public\Pictures
mklink /J "My Videos" C:\Users\Public\Videos
oh, thanks for the heads up, totally forgot about the Public/Default folders, and that we have mklink in Vista. ;-)
why does OSD mount the hard disk as X: ?
the hard disk is mounted as X: in refresh scenarios only. This is because the client reebots to a Windows PE image stored on the hard drive. The image gets the C: letter assigned when it boots up. So OSD then assigns the letter X: to the first partition on the hard drive.
Simple really :)
it really is :-)
and i guess there won't be a solution except for this workaround as long as windows is bound to drive letters.
Thanks so much for alerting me to this update. I'm still trying to wrap my head around the whole BDD way of doing things.
Currently I'm kicking off unattended windows XP installs from Win-PE using the winnt32.exe. I currently have about 30 distinct installs for both Windows XP and Windows 2003 using the $OEM$ network install method.
I see in the Distribution folder a $OEM$ folder, so I assume this method is also supported in the new Microsoft Deployment. Can you give a quick run down on how to migrate to this platform for legacy OS (xp / 2003) $OEM$ folders?
30 installs, thats alot :)
MDT will hopefully reduce then need for so many builds. You can create an $OEM$ folder for each task sequence you create in MDT.
Simply create a $OEM$ folder in the task sequence folder, i.e. \distribution\control\TSname\$OEM$
I'm having difficulities capturing an XP image. It works if I use the Source XP, but when I use a preveously captured XP.wim as a source I get errors during the capture phase.
I get an unhandled error by LTISysprep.
What is the exact error you are getting?
You may also want to have a look at the LTIsysprep.log file in the c:\minint\smsosd\osdlogs folder. This may give some suggestion as to why it is failing.
Using your batchfile to restore some junction points deleted by Creative driver installation programs. Thanks for posting it.
Creative driver installers delete the All Users and Default User junctions from the c:\users directory. I modified your batchfile to restore just these junctions:
However, after running your batchfile, I am able manually traverse the junctions - I can click on them and I am re-directed to the ProgramData and users\Default directories respectively.
Most other junctions don't allow this 'manual' behavior, giving just an 'Access Denied' message, which I thought was needed to prevent redundant backing up of data.
So is it normal to be able to traverse these junctions manually or should I be using the icacls command to deny access, similar to other lines in your batch file?
Thanks for your assistance. We've already alerted Creative to the problem, and at last report are attempting to reproduce the behavior.