Hello

We have recently upgraded and virtualized our K2000 appliance and will soon be upgrading most of our Windows XP boxes to Windows 7 Ent. We have a mid level and post level task on the 2000 to copy the Namedb.dat file on \\kbox2\petemp folder to the root of the C: and then to reference that .dat file to rename and  then join the domain. This no longer works because the xcopy command to copy the namedb.dat file now required credentials and xcopy is not built to include a username and pass in the command line.

Now on to my question...Is there a new slick way to accomplish a rename and join domain?

Answer Summary:
AndrewCPaquette | 08/31/2012 | OK I was able to solve this mystery Instead of using an xcopy command I did a net use that allows credentials. The new mid level task goes like this: net use t: PASSWORD /user:ADMIN xcopy /sei t:\namedb.dat c:\ I also found that the "xcopy /S /E /I source c:\source" command on the batch in the post install is pulling from a zip that was shipped up during the creation of the post install to \\kbox2\peinst\applications\25\contents\source Now that I figured that last piece out I was able to duplicate and modify my Windows7 rename join domain tasks.
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

2

Use a mid-level task to do the xcopy, you already have a map and are authenticated to petemp, so no credentials are needed.

A midlevel task is a post install task that has the runtime environment set to k2000 boot environment.

Corey
Lead L3 Enterprise Solutions Engineer, K2000
If my response was helpful, please rate it!

Answered 08/29/2012 by: cserrins
Red Belt

  • Corey

    I havent created a new mid and post task since we moved to Windows 7. I have a mid level task (Copy namedb.dat) that reads as follows:

    xcopy /sei t:\namedb.dat c:\kace\ (I'm assuming the t: Drive is the petemp folder here)


    I also have a post install (rename/join domain) task:
    call start_x86.bat


    The start_86x.bat is as follows:

    xcopy /S /E /I source c:\source
    c:\source\1_wsname_x86.bat (where is the "source" folder referring to?)

    This setup does not work in Windows 7. There is no Namedb.dat file moved to the newly imaged PC (C:\Kace) nor is there a folder created for path c:\source.

    I didn't create these tasks so I'm trying to dig into them and figure out what needs to be changed to accommodate the OS switch we have made. Also where is this 1_wsname_x86.bat file? I would like to see this in edit mode as well.

    Thank you in advance for your help
  • Accessing the petemp folder does require a password now. I think this is what is breaking the process.
Please log in to comment

Answers

1

I've used this before in the past. Not sure of your naming convention, but wsname covers a lot.

http://www.kace.com/support/resources/kb/article/How-to-rename-a-computer-and-join-it-to-a-Windows-domain-Image-Deployment

Answered 08/29/2012 by: dugullett
Red Belt

Please log in to comment
1

For the renaming you can use this Dell Kace program: http://www.kace.com/support/resources/kb/article/Get-Set-ComputerName

I always use a VBScript with a postinstallation task to add the computer. I recommend googling around to find one that works for you. There are quite a few out there.

 

Answered 08/29/2012 by: Ben M
Ninth Degree Black Belt

  • This content is currently hidden from public view.
    Reason: Removed by user request
    For more information, visit our FAQ's.
Please log in to comment
0

Alternatively you could use a method which we have here, using knit and sql drivers/queries you can get your machine name using an sql query to your K1 box during imaging and modify the unattend.xml file directly before it gets used.
This means you dont need to reboot after name changing, slick enough?
... pretty sure someone from the konference in Sydney last year still owes David and I a laptop for this one. The files are down in the comments (Courtesy of David as the originals got removed during the rollover from the appdeploy to itninja.)

http://www.itninja.com/question/name-machines-via-k1-with-k2-post-install-script

 

Answered 09/19/2012 by: Roonerspism
Second Degree Brown Belt

Please log in to comment
0

OK I was able to solve this mystery

Instead of using an xcopy command I did a net use that allows credentials. The new mid level task goes like this:

net use t: PASSWORD /user:ADMIN

xcopy /sei t:\namedb.dat c:\

I also found that the  "xcopy /S /E /I source c:\source" command on the batch in the post install is pulling from a zip that was shipped up during the creation of the post install to \\kbox2\peinst\applications\25\contents\source

Now that I figured that last piece out I was able to duplicate and modify my Windows7 rename join domain tasks.

Answered 08/31/2012 by: AndrewCPaquette
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity