• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Windows 7 not renaming, not joining to AD

    Scheduled Pinned Locked Moved
    FOG Problems
    2
    4
    3.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      andyroo54 Moderator
      last edited by

      Hi,
      Ok, so I’ve got a VM ready to upload, in fact I have uploaded it. Now before I upload, I have tried:

      Installed Fog service.
      Run Fogprep.
      Run windows sysprep and restart. Before it boots upload to Fog.

      Deploy image to new VM, it deploys perfectly except, FOG will not rename the PC, and it will not join to AD.

      So then I tried,

      Install Fog service and RESTART machine,
      Run Fogprep
      Run windows sysprep and restart. Before it boots upload to Fog.

      Either way Fog will NOT rename the machine, and it will NOT join to active directory.
      What am I doing wrong??

      Thanks,

      1 Reply Last reply Reply Quote 0
      • A
        andyroo54 Moderator
        last edited by

        Snapins deploy beautifully, just not renaming or AD joining?

        Maybe I should install the Fog service after the image has been deployed? Get it to run on first log on? Does the EXE work with a silent switch?

        1 Reply Last reply Reply Quote 0
        • M
          Markverg
          last edited by

          How many characters is your new and old hostname…
          There is a limitation to the number of characters, 11 or 13 max if i remember correctly.

          1 Reply Last reply Reply Quote 0
          • A
            andyroo54 Moderator
            last edited by

            Still having problems with this. It’s strange. I built a windows 7 pro image on a physical machine (samsung series 7 slate) and uploaded without sysprep because it was only to be deployed to the same hardware. But for whatever reason the virtual just won’t rename once it’s deployed to clients. I’ve tried installing the fog service both before/after sysprep and neither seems to work. Fog log doesn’t show any problems… I think anyway. Doesn’t show any tasks pending, but the host name in fog is totally different. Does the machine name have to be less than 15 characters when the fog service is installed maybe?

            20/02/2012 9:32 PM FOG::GreenFog No actions were found.
            20/02/2012 9:32 PM FOG::GreenFog No tasks found after validation!
            20/02/2012 9:32 PM FOG::GUIWatcher Dispatch OK!
            20/02/2012 9:32 PM FOG::printerManager Management level = 0
            20/02/2012 9:32 PM FOG::printerManager This host is set to NO MANAGEMENT, we will exit now.
            20/02/2012 9:32 PM FOG::printerManager Major printing operations complete, moving to tracking mode.
            20/02/2012 9:32 PM FOG::printerManager New user detected: WINDOW\Administrator
            20/02/2012 9:32 PM FOG::printerManager Waiting for tray to load…
            20/02/2012 9:32 PM FOG::DirCleaner Starting directory cleaning process…
            20/02/2012 9:32 PM FOG::DirCleaner Attempting to connect to fog server…
            20/02/2012 9:32 PM FOG::DirCleaner Module is active…
            20/02/2012 9:32 PM FOG::DirCleaner Determining which directories should be cleaned…
            20/02/2012 9:32 PM FOG::DirCleaner No directories are configured to be cleaned.
            20/02/2012 9:32 PM FOG::DirCleaner Starting directory cleaning loop…
            20/02/2012 9:32 PM FOG::DirCleaner Module has finished work and will now exit.
            20/02/2012 9:33 PM FOG::MODDebug Reading config settings…
            20/02/2012 9:33 PM FOG::MODDebug Reading of config settings passed.
            20/02/2012 9:33 PM FOG::MODDebug Starting Core processing…
            20/02/2012 9:33 PM FOG::MODDebug Operating System ID: 6
            20/02/2012 9:33 PM FOG::MODDebug Operating System Minor: 1
            20/02/2012 9:33 PM FOG::MODDebug MAC ID 0 00:0C:29:82:CB:AC
            20/02/2012 9:33 PM FOG::MODDebug MAC POST String: 00:0C:29:82:CB:AC
            20/02/2012 9:33 PM FOG::MODDebug A user is currently logged in
            20/02/2012 9:33 PM FOG::MODDebug Username: WINDOW\Administrator
            20/02/2012 9:33 PM FOG::MODDebug Hostname: WINDOW
            20/02/2012 9:33 PM FOG::MODDebug Attempting to open connect to: [url]http://fogserver/fog/service/debug.php[/url]
            20/02/2012 9:33 PM FOG::MODDebug Server responded with: Hello FOG Client
            20/02/2012 9:33 PM FOG::MODDebug Module has finished work and will now exit.

            Just confirmed that if I:

            Run sysprep, then upload and then deploy the image to another machine, (the PC name is 15 characters for some stupid reason, I can’t figure why my unattend.xml won’t specify the PC name, rather than giving it this random 15 character windows-wa532f2 name…), then rename the machine manually to a smaller name- THEN install fogservice and restart- THEN it will rename to the correct FOG name…

            So basically I need to rename the PC after sysprep to a short name (can probably do this with a powershell script), THEN get FOG service to install on SECOND start up… I wonder if I can even do that… “second” log on commands?

            1 Reply Last reply Reply Quote 0
            • 1 / 1
            • First post
              Last post

            217

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project