Windows AIK for Windows 7 is available for download
Grab it from the download center via https://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.)
Comments
Anonymous
January 01, 2003
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.Anonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
Hi 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. Regards AtolicaAnonymous
January 01, 2003
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 -MichaelAnonymous
January 01, 2003
What should I add to customsettings.ini so I won't be asked for username and password at "user credentials" - "specify credentials for connecting to network shares"??? Thanks againAnonymous
January 01, 2003
If autologon is enabled, the account is automatically enabled. If autologon is disabled, the account is automatically disabled. So there's no reason for the account to be disabled in the image - it doesn't matter. When the previously-captured image is deployed, assuming you are using MDT or have otherwise enabled autologon, you may want to disable the Administrator account at the end of the deployment process, when you no longer need it any more. That can be done with the command I provided, basically having the Administrator account turn itself off. -MichaelAnonymous
January 01, 2003
See the UserID, UserDomain, and UserPassword variables - you can set those in Bootstrap.ini so that the wizard doesn't need to prompt. -MichaelAnonymous
January 01, 2003
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.Anonymous
January 01, 2003
The space calculation issue is a known bug in MDT 2010 Beta 2. We will be releasing an RC version very soon that fixes this bug (and many more). -MichaelAnonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
ok 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?Anonymous
January 01, 2003
Until we release, it's just "best effort" support. Once the final release is out, we'd want you to upgrade as soon as possible. -MichaelAnonymous
January 01, 2003
We removed the logic from the LTISysprep.wsf script before releasing the RC, but the text wasn't removed from the release notes. We'll fix that too. -MichaelAnonymous
January 01, 2003
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). -MichaelAnonymous
January 01, 2003
So my question again. Is there a way to delete the Administrator account before or after sysprep kicks in? Thank youAnonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
I believe you are adding it to the wrong task sequence - you don't do it before you capture the image, you do it at the end of the process when you deploy that image (once you're finally done with the Administrator account). -MichaelAnonymous
January 01, 2003
For the WMPNetwk issue, this should be fixed in Windows 7 RTM. Is that what you are deploying, or are you still using Windows 7 RC? (This is a core operating system issue, not a WAIK or MDT issue.) For the other issues, I don't really have enough details to comment. Can you give Microsoft Support a call? -MichaelAnonymous
January 01, 2003
...and the media is not fully updated. I have to copy the Applications, Control and the rest of the folders from the distribution folder to the media.Anonymous
January 01, 2003
Hi Sorry for writing here, but I asked everywhere for help. Description 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 setupact.log: [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 ThanksAnonymous
January 01, 2003
Mike, Will this work with MDT 2008 or do you think that 2010 beta/rc is honestly stable enough for production use :) JasonAnonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
Not at all :-) The RC is due very, very soon, so I would wait for it before doing any production deployments. -MichaelAnonymous
January 01, 2003
Alright. I'll just read the known issues of the beta. Is that list exhaustive?Anonymous
January 01, 2003
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.Anonymous
January 01, 2003
Mike is there any idea of when the RC for MDT 2010 will be released?Anonymous
January 01, 2003
I meant "Still present in the RTM", but it was present in the RC too. (2 am here) Anyway, testing MDT 2010 RC as I'm typing this. Let's see what Santa has brought me.:)Anonymous
January 01, 2003
Why should I disable the admin aacount "after" i capture the image. Doesn't make sense. That's the whole purpose. I need to have the admin accoount disabled before the user reaches the welcome screen.Anonymous
January 01, 2003
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? Thank you. AtolicaAnonymous
January 01, 2003
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. Thank you.Anonymous
January 01, 2003
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.Anonymous
January 01, 2003
Can something be done? What am I doing wrong? I tried all sorts of things. Nothing works, the Administrator account is still there Thank youAnonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
Hi Michael I don't know if it is a bug or not, but every time I create a reference installation with MDT 2010 RC, Aero gets disabled. I have to use "Troubleshooting"-"Find and fix problems with transparency and other visual effects". This NEVER happened before with beta 2. I disabled drivers installation but same thing. The troubleshooter says that "Desktop Window Manager is disabled" even thoug "Desktop window manager" service is enabled. If I run the troubleshooter, it gets fixed. [IMG]http://i31.tinypic.com/2yjvomp.jpg[/IMG]Anonymous
January 01, 2003
Would production use of MDT 2010 be ok? We don't do anything complex.Anonymous
January 01, 2003
Ok. Does very soon mean this week? :)Anonymous
January 01, 2003
We did add that note specifically for the issue you are seeing since we knew it was an issue in Windows 7 RC. But our own testing with a post-RC build of Windows 7 didn't show this as a problem. We will try to verify this with Windows 7 build 7600.16385. -MichaelAnonymous
January 01, 2003
Is new WAIK compatible with MDT2010 Beta2? Can i just replace WAIK RC with new one? Is update datastore needed after that?Anonymous
January 01, 2003
This is a known (and documented) behavior that was present in Windows Vista and Windows 7. This is why MDT doesn't do things the way you describe: we modify the unattend.xml on the fly so that it contains both the computer name and the domain join credentials. -MichaelAnonymous
January 01, 2003
Quick question: Running Windows 7 RTM Enterprise. With sysprep and WAIK I have run into situation where if I have sysprep ask for a computer name it breaks the domain/client trust. This is the steps that seem to be happening:
- Sysprep creates a random computer name.
- Joins the domain.
- Sysprep then asks for a computer name, manual input.
- Renames computer.
- Domain/Client trust broken, because computer name does not match AD info. Is there anyway to move the step where it asks for a computer name, to a position before it joins the domain? Windows XP sysprep did this properly. Dan
Anonymous
January 01, 2003
I have given up. One more thing. As I don't have a domain set-up (testing for now), I can't join a domain when I'm prompted for network credentials. I want to capture the installation on a mapped network drive. I remember in the previous version I could open a dos prompt window and map a network drive(net use t:\ComputerNameShareName Password /user:ComputerNameUserName), when I filled the boxes which I can't in this version. A dos windows opens but only "ip configuration" show up. Is there any variable that lets me capture on the mappeed network drive? Thank you If IAnonymous
January 01, 2003
MDT 2008 will not work with Windows 7 or the new Windows Automated Installation Kit. MDT 2010 is required for that. -MichaelAnonymous
January 01, 2003
Hi, I am facing an issue after doing sysprep. Even after I have mentioned "autologon" entry in sysprep XML file, after the mini setup, I am getting an error "Username or password not correct". If I enter the same password for the account, it allows me to log in. I have tried with plain text as well as encrypted text for password entry. FYI, I am syspreping with my own XML file and same sysprep command specified in LTISysprep.wsf. Also I am running the cleanup script for previous autologon entries before sysprep. Highly appreciate your help. Thanks, JibuAnonymous
January 01, 2003
Very soon :-)Anonymous
January 01, 2003
Quick question: Running Windows 7 RTM Enterprise. With sysprep and WAIK I have run into situation where if I have sysprep ask for a computer name it breaks the domain/client trust. This is the steps that seem to be happening:
- Sysprep creates a random computer name.
- Joins the doman.
- Sysprep then asks for a computer name, manual input.
- Renames computer.
- Domain/Client trust broken, because computer name does not match AD info. Is there anyway to move the step where it asks for a computer name, to a position before it joins the domain? Windows XP sysprep did this properly. Dan