+ Post New Thread
Page 2 of 2 FirstFirst 12
Results 16 to 26 of 26
Windows Thread, Sysprep help Please in Technical; I didnt realise sysprep could take the computer name from AD. Thought it was only using RIS where it does ...
  1. #16
    tarquel's Avatar
    Join Date
    Jun 2005
    Location
    Powys, Mid-Wales, UK
    Posts
    1,740
    Thank Post
    13
    Thanked 45 Times in 35 Posts
    Rep Power
    29
    I didnt realise sysprep could take the computer name from AD. Thought it was only using RIS where it does that.

    Guess I've learnt something new there, but no, the only way around it i guess is to manually enter it.

    Thats what i did when i used to sysprep computers before RIS.

  2. #17
    jsnetman's Avatar
    Join Date
    Oct 2007
    Posts
    887
    Thank Post
    23
    Thanked 134 Times in 126 Posts
    Rep Power
    40
    I've got in installing the drivers but it won't pick the machine name out of AD
    You can get sysprep to automatically assign a random name beginning with say "myschool" which would give you computer name like "myschool1,2,3 and so on. But you cant get sysprep to pull the name from AD.

  3. #18
    tarquel's Avatar
    Join Date
    Jun 2005
    Location
    Powys, Mid-Wales, UK
    Posts
    1,740
    Thank Post
    13
    Thanked 45 Times in 35 Posts
    Rep Power
    29
    Sorry. I wasn't clear in my post. I meant to put:

    "I knew you could generate the computer name automatically to use, but didnt realise sysprep could take the computer name from AD"

    Been doing it various with UA installs for many a year.... which is why i didnt think that you could automatically retrieve the computername from AD [except by using RIS / another 3rd party deployment method].

  4. #19

    Join Date
    Apr 2006
    Location
    Bamber Bridge
    Posts
    192
    Thank Post
    3
    Thanked 10 Times in 10 Posts
    Rep Power
    19
    Well to drag this back up, I couldn't get the machines with the Pro100/VE entwork connection to pick the name out of AD but if I use another supported network card it does. I've now got all my machines staged in AD and the sysprep.inf file pulls the computername down from AD. I think it does this when you use the RIS or WDS part to setup. I can't tell you how it works but it does and it's saved me a lot of time. No more moving computer accounts between OU's, no more renaming, unless I change the motherboard!! If anyone wants any more info on this just PM me and I'll see if I can guide you in the right direction

  5. #20
    jsnetman's Avatar
    Join Date
    Oct 2007
    Posts
    887
    Thank Post
    23
    Thanked 134 Times in 126 Posts
    Rep Power
    40
    So let me get this clear, on a normal rebuild you just set it away and you do not use any sort of input like machine name in the mini setup.

  6. #21

    Join Date
    Apr 2006
    Location
    Bamber Bridge
    Posts
    192
    Thank Post
    3
    Thanked 10 Times in 10 Posts
    Rep Power
    19
    Quote Originally Posted by jsnetman View Post
    So let me get this clear, on a normal rebuild you just set it away and you do not use any sort of input like machine name in the mini setup.
    Thats right, my sysprep.inf file has the reference %AMCHINENAME% for the machine name and %MACHINEDOMAIN% for the domain to join. All I do is boot machine via PXE to WDS, set it to pull the image down, and after 10 mins it's sat at the logon box waiting to be used.

    If you want a copy of my sysprep.inf file i'll happily post it up here.

  7. #22
    jsnetman's Avatar
    Join Date
    Oct 2007
    Posts
    887
    Thank Post
    23
    Thanked 134 Times in 126 Posts
    Rep Power
    40
    Ok yes it's pre-staging, are these machines with intel cards new to your network.

  8. #23

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,572 Times in 1,252 Posts
    Rep Power
    340
    Thats right, my sysprep.inf file has the reference %AMCHINENAME% for the machine name and %MACHINEDOMAIN% for the domain to join. All I do is boot machine via PXE to WDS, set it to pull the image down, and after 10 mins it's sat at the logon box waiting to be used.
    I was under the impression you can either get Sysprep to randomly create a computer name based on domain name, specify a list of computer names it can use or you manually specify a computer name during Mini Setup. I always specify the computer name manually, because it's impossible to get Sysprep to use computer names alphanumerically.

    As for pulling the computer names down, I'm not so sure about that. I can only presume you've specified a list of computer names for Sysprep to use and have already created new computer objects in AD, with the correct OU. I can't see how the computer name would be pulled down from AD.

    The Mini Setup process itself requires you to specify the computer name (using whatever method) before joining the domain, so I doubt it's pulling the names down from AD, but more likely an answer file with computer names.

  9. #24
    jsnetman's Avatar
    Join Date
    Oct 2007
    Posts
    887
    Thank Post
    23
    Thanked 134 Times in 126 Posts
    Rep Power
    40
    If you are using RIS or WDS you can prestage them with the GUID and the settings in sysprep will pull the name down because the GUID matches. If the guy with the problem has added new machines to the network he has to pre-stage them as Geoff suggested in a previous post in this thread.

  10. #25
    torledo's Avatar
    Join Date
    Oct 2007
    Posts
    2,928
    Thank Post
    168
    Thanked 155 Times in 126 Posts
    Rep Power
    48
    Quote Originally Posted by Ste_Harve View Post
    Thats right, my sysprep.inf file has the reference %AMCHINENAME% for the machine name and %MACHINEDOMAIN% for the domain to join. All I do is boot machine via PXE to WDS, set it to pull the image down, and after 10 mins it's sat at the logon box waiting to be used.

    If you want a copy of my sysprep.inf file i'll happily post it up here.
    if you could ste, that would be great.

  11. #26

    Join Date
    Apr 2006
    Location
    Bamber Bridge
    Posts
    192
    Thank Post
    3
    Thanked 10 Times in 10 Posts
    Rep Power
    19
    Here's my sysprep.inf file which allows me to set a machine imaging and leave it. When it's rebooted it's ready for use with the staged name and GUID in AD.

    ;SetupMgrTag
    [Unattended]
    OemSkipEula=Yes
    DriverSigningPolicy=Ignore
    NonDriverSigningPolicy=Ignore
    OEMPNPDriversPath=\Drivers\NIC;Drivers\NIC\Realtek ;Driver\NIC\Broadcom
    UpdateInstalledDrivers=Yes
    LegacyNIC = 1

    [UserData]
    ProductID=*****************
    FullName = "Walton-le-Dale Arts College & High School"
    OrgName = "Preston"
    ComputerName = %MACHINENAME%

    [RegionalSettings]
    LanguageGroup=1
    SystemLocale=00000809
    UserLocale=00000809
    InputLocale=0809:00000809

    [GuiUnattended]
    AdminPassword="*********"
    EncryptedAdminPassword=NO
    OemSkipWelcome = 1
    OemSkipRegional = 1
    TimeZone = %TIMEZONE%

    [Display]
    BitsPerPel = 32
    XResolution = 1024
    YResolution = 768
    VRefresh = 60

    [Networking]

    [NetServices]
    MS_Server=params.MS_PSched

    [Identification]
    JoinDomain = %MACHINEDOMAIN%
    DoOldStyleDomainJoin = Yes

SHARE:
+ Post New Thread
Page 2 of 2 FirstFirst 12

Similar Threads

  1. Sysprep & Ghost
    By cgiuk in forum How do you do....it?
    Replies: 13
    Last Post: 26th November 2007, 09:14 AM
  2. RIS/Sysprep problem
    By Gatt in forum Windows
    Replies: 3
    Last Post: 17th August 2006, 11:44 AM
  3. Sysprep
    By tosca925 in forum Windows
    Replies: 14
    Last Post: 7th April 2006, 01:53 PM
  4. Activate before Sysprep
    By thom in forum Windows
    Replies: 10
    Last Post: 4th April 2006, 03:30 PM
  5. Why isn't sysprep working?
    By Ric_ in forum Windows
    Replies: 10
    Last Post: 16th January 2006, 03:00 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •