Server name assigned before scripted install

[Juan Castillos]

Can you assign the server name to the server in RDP before the scripted install occurs? I have had a problem doing this. After the installation, whenever I try to change the servers config in any way, I get access denied errors - even when logged into the server as local admin or domain admin. This is Windows 2000 Server SP4.

[Jeffrey Yadzinski_2 · Accepted solution]

I had this exact problem. I could not get it to work, period. I think I tried just about everything. I just went back to letting RDP assign it the Serial Number, and allowing it to build that way. I believe it has something to do with the SID and whether or not a server of the same name was previously on the network domain you are installing the server to.

Hope this helps...

[Jeffrey Yadzinski_2]

By the way, I also tried setting the server name to a name I knew never existed on the network, and I still had the same issue. MY prolem is unique however, because of how tight our security is. LMHash problems and sexurity settings in W2K3.

[Juan Castillos]

Thank you Jeffery. But I am W2K and why would they put the feature into the program if it does not work? What I am saying is, why bother allowing us to change something that is only leading to a mad situation?

[Jeffrey Yadzinski_2]

That is the golden question Juan. Why would ANY company put a feature in an application that would cause a problem. I do not think it is the application, in this case however. I am just not sure wat it is. Until I can do further testing, we will have to wait for someone else to assist. Sorry I cannot offer more insight. I do not think it has to do with the OS either, but we'll see.

[Tv_3]

Hi,µ

you can use the sed.exe commando, to change on the fly some values within your unattend.txt file.

let me say you have originaly in your unattend file

computername=*.

By using the sed commando you can search after "computername=*" and replace it with "computername=Myserver_Name"

[Matt_253]

Hello,
This is quite easy to do and is useful when you have a new load of servers.

Note down the Serial number(s) of the server(s)either via the white label or via the bios.

Use the import computer option and either import using pre prepared csv file (here is a sample one supplied with RDP)or the add computer option.

Key in the computer name and then key in the serial number in the obvious fields.
( you can also use a MAc address ).

A computer icon will appear and this will be yellow to indicate that it is unrecognized.
once a server has gone through the usual PXE process the server icon should turn to a grey one. This will also work if the computer is showing as a new computer in the RDP console.

Drag your scripted job onto the server and bobs your uncle.

[Dan White_1]

In you default unattend file (the one specified in the copy Altiris files section), change the computername= line to

ComputerName=%#!computer@right(name,15)%

The line that reads replacetokens...is what does this.

This will set the name to the first 15 charactors of the display name in the console. If you want to change the name of the server, just change it in the console and drop your build script.

[Jeff F]

Hi, how does this work? I put that exact phrase in my unattend file so that I can prename the computers but when the install is midway, where it would ask for the name, it says invalid name and shows that it was trying to use: %#!computer@right(name,15)% as its name, which means it's not reading it properly... any ideas?

[Dan White_1]

Are you using the default events that come integrated with RDP? There should be a script task in you rbuild event that looks like the picture attached. The line that reads "rem replacetokens..." is what changes the unattend.txt. Don't let the "rem" fool you...the script still processes the line. Look at the picture I attached and just change the paths to suit your envirnment.

[Dan White_1]

Here is the picture...

[Jeff F]

I've attached what I have in our script... where you see "***" is where i had that name command trying to get it to read in the name...

Thanks for your quick response and for helping me out.

J


rem Install OS
rem bootwork unload
set ss=ss.710
set os=wnet
set unattendfile=wnet.txt
****
call f:\deploy\tools\scripts\wnet.bat

[Dan White_1]

So you are using an older version of RDP. I am not sure if "replacetokens" works in the older versions. In the older version, I used to use the %NAME% variable to set the machine name. I'm sure of the exact details. If you concider upgrading to RDP 2.1 you will thank yourself later!

[Jeff F]

Dan, I wish I could give you some points for helping me... with a little time into it and not asking help on every little thing, i finalyl figured it out and have the name function working as I wanted it to. Thanks for the head start.

j

[Dan White_1]

I take beer as well as points! :)

[Jeff F]

I have shipped a case of Guinness via BPS (Beer Postal Service) which should be getting there to you by tonight. Check your local bar, it'll be there.