Grab it from the download center via http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=696dd665-9f76-4177-a811-39c26d3b3b34. (Remember that the new USMT 4.0 bits are included in Windows AIK too.)
Is new WAIK compatible with MDT2010 Beta2?
Can i just replace WAIK RC with new one?
Is update datastore needed after that?
Sorry for writing here, but I asked everywhere for help.
I finished building my master installation of win 7 using MDT beta 2 and sysprepped it using the default task which runs LTISysprep.wsf. I got to the mini setup step, but the Administrator account still exists. Shouldn't the Administrator account be removed by running LTISysprep.wsf ?????
The log says that it has been removed
[msoobe.exe] Successfully removed administrator profile
So the administrator account should be disabled or removed, but it isn't.
If I run sysprep.exe /generalize /oobe /shutdown manually the administrator account is removed as it should. I checked unattend.xml in WSIM, and there's a TempAccount created during oobe step and autlogon for Administrator account is set to 999. Should I replace LTISysprep.wsf with "sysprep.exe /generalize /oobe /shutdown" ??????
I posted this on deploymentguys blog also and on connect but didn't get an answer yet.
What am I doing wrong? Isn't LTIsysprep.wsf suppose to remove the Administrator account.
I am using the latest Windows 7 AIK
MDT 2010 Beta 2 will work with the RTM version of Windows AIK, but we'll be releasing MDT 2010 RC shortly so that will soon be the preferred release.
Sysprep won't remove the Administrator account (that account is never removed), it will just remove the profile. The account will be disabled, but if autologon is specified in the unattend.xml it will be re-enabled when the image is deployed.
Since LTI always uses autologon, the Administrator account will always be enabled.
As I understand the applications are getting installed during oobe pass inside the Administrator logged on session. Isn't there a way to modify unattend.xml and disable the Administrator account, but not break the default MDT task?? I want it to run and reach the capture step.
If I disable autologon in pass 7 oobe, the applications will fail to install. Probably I will be best to install them during audit mode, but MDT seems not to work this way. Or will it?
I hope you understand what I'm trying to do.
MDT installs applications via autologon only, after OOBE has completed. We do not use audit mode.
The main reasons for autologon: simplicity, compatibility (many application installers have issues when run without the shell being active), and flexibility (we may need multiple reboots, something that doesn't work so well in OOBE).
So here goes my question again.
Is there a way to delete the Administrator account before sysprep kicks in?
Can I modify unattend.xml to do that?
So my question again.
Is there a way to delete the Administrator account before or after sysprep kicks in?
Before? No, I believe the specialize process will put it back. After? Don't know, but generally I wouldn't recommend it. Keeping it disabled is preferred, and disabling it is pretty simple.
How do I keep it disabled? I tested the installation and after minisetup oobe runs and the welcome screen comes in I have the Administrator account listed besides the local account one created at oobe step.
I want it gone.
I know autologon option in unattend.xml is the one to blame, but it is specified twice in the xml. What to delete? Can I tweak anything else?
Just add a step at the end of the task sequence that runs the command to disable the local Administrator account:
net.exe user Administrator /active:no
Already did that, but I did put the command after LTIsysprep.wsf and didn't work. Let's see if it'll work when running last.
Mike is there any idea of when the RC for MDT 2010 will be released?
Very soon :-)
net.exe user Administrator /active:no didn't disable the Administrator account.
It's still listed at welcome screen after creating the user account.
Kinda lost here.