Windows AIK for Windows 7 is available for download


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.)


Comments (47)
  1. Anonymous says:

    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.

  2. Anonymous says:

    I added "net user administrator /active:no", right after "Execute sysprep".

    Here’s a pic:

    http://i29.tinypic.com/10wqlx3.jpg

  3. Anonymous says:

    Also in the release notes it says:

    โ€ข Because of a bug in Windows 7, the System Preparation Tool (Sysprep) fails to execute when the Windows Media® Player Network Sharing Service is running. The LTISysprep.wsf script contains a workaround for this problem, but the workaround does not work on nonโ€“English language versions of Windows 7. Update the LTISysprep.wsf script as follows to resolve this issue:

    1. Locate the existing code:

    oShell.Run "net stop ""Windows Media Player Network Sharing Service""", 0, true

    2. Update the code to reflect the changes below:

    oShell.Run "net stop WMPNetworkSVC", 0, true

    I can’t find that code anywhere inside LTISysprep.wsf

  4. Anonymous says:

    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

    Atolica

  5. Anonymous says:

    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

    -Michael

  6. Anonymous says:

    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 again

  7. Anonymous says:

    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.

    -Michael

  8. Anonymous says:

    See the UserID, UserDomain, and UserPassword variables – you can set those in Bootstrap.ini so that the wizard doesn’t need to prompt.

    -Michael

  9. Anonymous says:

    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.

  10. Anonymous says:

    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).

    -Michael

  11. Anonymous says:

    Michael

    What about that damn Administrator account? ๐Ÿ™‚

  12. Anonymous says:

    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?

  13. Anonymous says:

    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.

    -Michael

  14. Anonymous says:

    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.

    -Michael

  15. Anonymous says:

    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).

    -Michael

  16. Anonymous says:

    So my question again.

    Is there a way to delete the Administrator account before or after sysprep kicks in?

    Thank you

  17. Anonymous says:

    Hi

    I am very close to finish building a master wim image of a Windows 7 installation that I will deploy on 50 computers. After trial and error numerous attempts and using MDT beta 2 (waiting for MDT RC though) I successfully tweaked the installation, installed applications but I stumbled upon several issues.

    No matter what I do the power plan set in unattend.xml created with WSIM, doesn’t get implemented in the final installation.

    I modified Microsoft-Windows-powercpl in specialize and generalize pass and entered my preferred power scheme, in my case 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c  (High performance), but the power scheme that sets up is the same, the default one, Balanced powerscheme.

    I also tried to set this by running sysprep /generalize /oobe /shutdown /unattend:<path to unattend.xml>, having the poweplan set in the unattend.xml file. Doesn’t work. Then I thought of running sysprep without /generalize option. Doesn’t work either.

    I copied the default profile using CopyProfile setting which enables to customize a profile and all the new profiles created, with settings from the default user profile (Administrator account). This I found to be very handy as it should retain the settings set up by the default account used for reference installation, even after running sysprep /generalize. Be serious. Doesn’t work.

    So after almost a week of testing and 20 installations, tweaking and various scenarious I reached to several conclusions:

    WAIK or Windows 7 are buggy. Sysprep still has the media player sharing drm license UBERBUG, that is I always have to kill  WMPNetwk.exe process before running sysprep.

    None of the settings fed to sysprep by /unattend:*.xml switch don’t get set up in the final installation, and neither when running a normal unattended installation using unattend.xml.

    So I am 100% positive this is an omission on Microsoft’s part. Sysprep is still buggy since Windows 7 Beta build 7000, Still present in the RC.

    I hope someone from MS or dealing with WAIK would give me a few answers. I find xml scripting language ideal for unattended installations, deployment,  but it’s a pain in the backside when things don’t work.

    Atolica

  18. Anonymous says:

    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).

    -Michael

  19. Anonymous says:

    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?

    -Michael

  20. Anonymous says:

    …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.

  21. Anonymous says:

    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

    Thanks

  22. Anonymous says:

    Mike,

    Will this work with MDT 2008 or do you think that 2010 beta/rc is honestly stable enough for production use ๐Ÿ™‚

    Jason

  23. Anonymous says:

    Thanks, but can’t seem to find the right moment to run net.exe user Administrator /active:no(see the above image – is that correct?). I tried all the sequences possible, but the administrator account is still on at welcome screen after setting the local account (oobe).

    Using the default task, I have a TempAccount logged on (inside unattend.xml). That’s the last autologon task.

    another issue i have is updating media, flash drive and network share.

    This error comes up in both cases: "The specified drive O:\ContentDeploy does not have enough free space for the source files to be copied to it (53673904050 bytes needed, 3941827338 bytes", even if I have a 4 gb flash drive and 14 gb free space on network share.

    Thank you

  24. Anonymous says:

    Not at all ๐Ÿ™‚  The RC is due very, very soon, so I would wait for it before doing any production deployments.

    -Michael

  25. Anonymous says:

    Alright. I’ll just read the known issues of the beta. Is that list exhaustive?

  26. Anonymous says:

    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.

  27. Anonymous says:

    Mike is there any idea of when the RC for MDT 2010 will be released?

  28. Anonymous says:

    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.:)

  29. Anonymous says:

    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.

  30. Anonymous says:

    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.

    Atolica

  31. Anonymous says:

    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.

  32. Anonymous says:

    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.

  33. Anonymous says:

    Can something be done? What am I doing wrong? I tried all sorts of things. Nothing works, the Administrator account is still there

    Thank you

  34. Anonymous says:

    The WMPNetwk issue is not fixed in the RTM. I came to this conclusion after days of testing. If the process runs sysprep hangs.

    I just took a look over the MDT 2010 RC "Release Notes.doc" and it clearly stated "Because of a bug in Windows 7, the System Preparation Tool (Sysprep) fails to execute when the Windows Media® Player Network Sharing Service is running." Did you write that?:)

  35. Anonymous says:

    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]

  36. Anonymous says:

    Would production use of MDT 2010 be ok? We don’t do anything complex.

  37. Anonymous says:

    Ok. Does very soon mean this week? ๐Ÿ™‚

  38. Anonymous says:

    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.

    -Michael

  39. Anonymous says:

    Is new WAIK compatible with MDT2010 Beta2?

    Can i just replace WAIK RC with new one?

    Is update datastore needed after that?

  40. Anonymous says:

    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.

    -Michael

  41. Anonymous says:

    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:

    1. Sysprep creates a random computer name.

    2. Joins the domain.

    3. Sysprep then asks for a computer name, manual input.

    4. Renames computer.

    5. 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

  42. Anonymous says:

    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 I

  43. Anonymous says:

    MDT 2008 will not work with Windows 7 or the new Windows Automated Installation Kit.  MDT 2010 is required for that.

    -Michael

  44. Anonymous says:

    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,

    Jibu

  45. Anonymous says:

    Very soon ๐Ÿ™‚

  46. Anonymous says:

    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:

    1. Sysprep creates a random computer name.

    2. Joins the doman.

    3. Sysprep then asks for a computer name, manual input.

    4. Renames computer.

    5. 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

  47. showbox says:

    Thanks for the great info. I really loved this. I would like to apprentice at the same time as you amend your web site, how could i subscribe for a blog site?
    For more info on showbox please refer below sites:
    http://showboxandroids.com/showbox-apk/
    http://showboxappandroid.com/
    Latest version of Showbox App download for all android smart phones and tablets.
    http://movieboxappdownloads.com/ – Itโ€™s just 2 MB file you can easily get it on your android device without much trouble. Showbox app was well designed application for android to watch movies and TV shows, Cartoons and many more such things on your smartphone.
    For showbox on iOS (iPhone/iPad), please read below articles:
    http://showboxappk.com/showbox-for-ipad-download/
    http://showboxappk.com/showbox-for-iphone/
    Showbox for PC articles:
    http://showboxandroids.com/showbox-for-pc/
    http://showboxappandroid.com/showbox-for-pc-download/
    http://showboxforpcs.com/
    There are countless for PC clients as it is essentially easy to understand, simple to introduce, gives continuous administration, effectively reasonable. it is accessible at completely free of expense i.e., there will be no establishment charges and after establishment
    it doesn’t charge cash for watching films and recordings. Not simply watching, it likewise offers alternative to download recordings and motion pictures. The accompanying are the strides that are to be taken after to introduce Showbox application on Android.
    The above all else thing to be done is, go to the Security Settings on your Android telephone, Scroll down and tap on ‘Obscure sources’.

Comments are closed.