FOG Auto Join to AD



  • Hi all.

    I have an interesting issue were i believe FOG fog auto join to AD is shutting down my newly imaged systems without my sysprep file finishing all of its first time login commands.

    Has anyone else had issues with this?

    is there a way i can delay how quickly fog renames and joins the computer to AD to give it some more time to load all the first time login scripts?

    Im running Fog 1.1.2

    Im using sysprep to run a first time login script with the local admin account to activate our installation of office 2010.

    Im running two login scripts, 1 that activates the OS and and 2nd that activates Office 2010.

    Thanks!



  • Thanks all I was on the right path but now i’ve got it working just right thanks for the help!
    Incase it helps anyone else here is the FirstLogin Commands i use to auto activate windows 7 OS and Microsoft office 2010 using sysprep

    [CODE] <FirstLogonCommands>
    <SynchronousCommand wcm:action=“add”>
    <CommandLine>cscript /b c:\windows\system32\slmgr.vbs /ato</CommandLine>
    <Order>1</Order>
    <RequiresUserInput>false</RequiresUserInput>
    <Description>Act OS</Description>
    </SynchronousCommand>
    <SynchronousCommand wcm:action=“add”>
    <Order>2</Order>
    <CommandLine>cscript “C:\Program Files (x86)\Microsoft Office\Office14\ospp.vbs” /act</CommandLine>
    <RequiresUserInput>false</RequiresUserInput>
    <Description>Act Offfice</Description>
    </SynchronousCommand>
    <SynchronousCommand wcm:action=“add”>
    <CommandLine>sc config “FOG Service” start= auto</CommandLine>
    <Order>4</Order>
    <Description>Change FOG service from delay to Automatic</Description>
    </SynchronousCommand>
    <SynchronousCommand wcm:action=“add”>
    <CommandLine>timeout 20</CommandLine>
    <Description>Pause for 20 seconds</Description>
    <Order>3</Order>
    </SynchronousCommand>
    <SynchronousCommand wcm:action=“add”>
    <Order>5</Order>
    <Description>Enable the fog service</Description>
    <CommandLine>net start “FOG Service”</CommandLine>
    </SynchronousCommand>
    </FirstLogonCommands>[/CODE]


  • Moderator

    Right after I install the FOG client, I set the service to startup type: manual and stop the service. Then I use a command at the end of my setup script to set the startup type to automatic and start the service.


  • Senior Developer

    Many times, if you’ve sysprepped the image and have fog client installed, from the setupcomplete.cmd script you’d start it with net stop “FOG Service”. It will then run the scripts as expected. At the end of the tasks to be performed you’d re-enable the fog cservice with: net start “FOG Service”



  • [quote=“kelly.bettendorf, post: 33689, member: 5100”]Hi all.

    I have an interesting issue were i believe FOG fog auto join to AD is shutting down my newly imaged systems without my sysprep file finishing all of its first time login commands.

    Has anyone else had issues with this?

    is there a way i can delay how quickly fog renames and joins the computer to AD to give it some more time to load all the first time login scripts?

    Im running Fog 1.1.2

    Im using sysprep to run a first time login script with the local admin account to activate our installation of office 2010.

    Im running two login scripts, 1 that activates the OS and and 2nd that activates Office 2010.

    Thanks![/quote]

    TO add some more detail,

    when i don’t have auto join to AD enabled on my testbox all of my first time login scripts run as they should.
    Ive added a 30 second timeout command at the end to see if that makes any difference.

    I will test and report back my findings.


Log in to reply
 

449
Online

39.4k
Users

11.1k
Topics

105.5k
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.