/build/static/layout/Breadcrumb_cap_w.png

K2000 Image Deployment - Straight into desktop

I've looked through the threads and am not really finding anything specific to my issue, so I apologize if this has been covered.

I have a Windows 7 Enterprise (x64) image that I sysprep'd to a shutdown and then captured as a K-Image on the K2000.  It also has the unattend.xml that I built out Windows System Image Manager.  On the K2000, I have some post install tasks that rename the PC and joins it to the domain.  What happens upon deployment is that drops me at the windows setup screen where it asks me to create a user and name the pc.  I do that and then it asks me to accept the EULA.  I do that.  Then it asks me to login.  Once I do that, it drops me on the desktop and then nothing happens.  Nothing kicks off in regards to joining the domain.  If I go into the system settings, next to the computer name, it says that a rename is pending and will take effect on reboot.  I manually reboot, login, and check; the computer did change like it said it would, but that's it.  No joining of the domain or anything.  I will say that I'm most familiar with scripted installs and the pre and post install tasks function as they should, for the most part.  Perhaps there is something I'm missing, or not doing correctly? 

Any help would be great.

Thanks!

Asked 8 years ago 1341 views
0 Comments   [ + ] Show comments

Answers (2)

Posted by: SMal.tmcc 8 years ago
Red Belt
0
sounds like your unattended file is bad or for the wrong os version.  That is why those extra questions are popping up
Posted by: chucksteel 8 years ago
Red Belt
0
If your unattend file doesn't create a user then Windows will prompt to create one in OOBE. To get around this you can create a user (I call mine temp) and then run a first login command to delete that user.
                <SynchronousCommand wcm:action="add">
                    <CommandLine>net user temp /delete</CommandLine>
                    <Description>Delete Temp User Account</Description>
                    <Order>2</Order>
                    <RequiresUserInput>false</RequiresUserInput>
                </SynchronousCommand>
The K2000 should be setting up a run key that will kick off the process that runs your post-install tasks. If you didn't set an autologin in your unattend file then there might be a problem with that. Be sure to specify and autologin to an administrator account that will login enough times to cover any reboots required by your post-install tasks.



Comments:
  • So it turns out that I was using the the unattend file incorrectly. I thought that I could just drop the unattend.xml file into the c:\windows\panther directory, that the first boot would use it.

    Now I'm running into an issue where after I sysprep with the unattend file included, on first boot, it runs through but instead of dropping me on the desktop using autologon, it leaves me on the setup screen with the next option. If I click "Next" it then has a window popup stating that it's finalizing settings and then autologons like it should. Why am I still seeing the last part of the setup?

    Thanks!

    **btw.....I wasn't aware that I could add synchronous commands as you've shown; that could be a big help in the future. - captains1stm8 8 years ago
    • If the next setup screen is the EULA then make sure that you hide the EULA page. In System Image Manager look under OOBE, Windows Shell Setup, OOBE, Hide EULA Page. - chucksteel 8 years ago
      • I have the EULA page set, but what I'm seeing is not the EULA. I can reimage that machine here in a few mins, but it's just a screen stating that we're going to setup windows and a next button. I click next and it says it's finalizing. That's it. - captains1stm8 8 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ