Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

prestage & machinename

- - - - -

  • Please log in to reply
3 replies to this topic

#1
lasswellt

lasswellt

    Newbie

  • Member
  • 10 posts
  • Joined 19-October 05
Now my understanding was the prestaging process was to allow for preassigning machine names and having them managed by the RIS server.

My network is configured in such a way that the machine name has to be created before it is joined to the domain, which is where I would like prestaging to come into play.

What do i need to add to my SIF file to have it make the computer name based on it's counterpart in AD?


How to remove advertisement from MSFN

#2
InTheWayBoy

InTheWayBoy

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 709 posts
  • Joined 16-August 04
%MACHINENAME% is the variable...the question I have is have you entered in the clients GUID when you made the computer account? As far as I know that is the only way to utilize that variable, so make sure you have that field populated.

#3
RogueSpear

RogueSpear

    OS: SimplyMEPIS

  • MSFN Sponsor
  • 1,529 posts
  • Joined 18-September 04
And if the GUID isn't readily available you can use the MAC address preceeded with twenty zeros (0). In fact I find this preferrable in some circumstances. If you have any computers that are around 5 years old or so, take note as there were some vendors (Toshiba cough cough) that made a major boo boo by hardcoding the same GUID into a BIOS update. So when you install your second computer, it disjoins the first one from the domain :blink: and if you're like me, you disable the local admin account, which makes for a neutered computer.

Also try to prestage your computers into the appropriate OU so that any GPO based application deployments take place automatically after setup has completed.

#4
lasswellt

lasswellt

    Newbie

  • Member
  • 10 posts
  • Joined 19-October 05

%MACHINENAME% is the variable...the question I have is have you entered in the clients GUID when you made the computer account? As far as I know that is the only way to utilize that variable, so make sure you have that field populated.


Yes, I entered the approporiate GUID when adding the computer account, but it still tries to add it as the default for RIS (USERNAME# i believe) which is unallowed in our AD structure.

And if the GUID isn't readily available you can use the MAC address preceeded with twenty zeros (0). In fact I find this preferrable in some circumstances. If you have any computers that are around 5 years old or so, take note as there were some vendors (Toshiba cough cough) that made a major boo boo by hardcoding the same GUID into a BIOS update. So when you install your second computer, it disjoins the first one from the domain :blink: and if you're like me, you disable the local admin account, which makes for a neutered computer.

Also try to prestage your computers into the appropriate OU so that any GPO based application deployments take place automatically after setup has completed.


This is very good to know. Maybe the script I ran to uncover the GUID for that machine messed up. I'll try that as the GUID and see if this solves the problem. Thanks guys.

Any other hints would be much appreciated, the %MACHINENAME% attrib is being used currently (no adjustments have been made to the stock sif file yet... just trying to get the basics before everything else gets done).




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users