FirstLogon / LogonCommands on CORE not working?

Answered FirstLogon / LogonCommands on CORE not working?

  • Monday, November 06, 2006 4:42 PM
     
     

    Hi,

    I cannot seem to get any commands to run using either FirstLogon or LogonCommands.

     

    This functionality works fine on Longhorn Standard edition, but I get nothing on CORE. I can see the xml being parsed correctly in the Panther logs, but no evidence that anything actually executed.

     

    Is this a known issue with build 5600, or a limitation of CORE?

    Cheers,

    Andy

All Replies

  • Monday, November 06, 2006 7:06 PM
    Owner
     
     

    Hi,

    Are you referring to the unattend options? These use the Run and Runonce registry keys which are not supported on Server Core.

    Andrew

  • Tuesday, November 07, 2006 9:07 AM
     
     

    Hi Andrew,

    Yes, I was talking about unattended install, thanks for the information that I can't use these options on Core, my gut feeling told me I was fighting a losing battle.

    If these options are not supported then should they be removed from the catalog for STANDARDCORE when viewed in System Image Manager?

    Maybe that is just a beta bug, so more importantly, what is the replacement mechanism for Run / RunOnce on Core? Are we left with only what is exposed through components and packages?

     

    Cheers

    Andy

  • Tuesday, November 07, 2006 4:59 PM
    Owner
     
     Answered

    Hi,

    The reason these don't work is that they are actually processed by Explorer.exe at logon and there is no Explorer in Server Core.

    Yes, they really shouldn't be appearing in System Image Manager, I'll pass this along. However, the way System Image Manager creates the catalog it may be that these settings are defined in something included in Server Core, but the code that processes them isn't.

    You only have what is exposed through the components and packages for Server Core. We recently became aware of another way to execute commands through unattend that we are experimenting with. So far it is working, but it does require manually editing the unattend file. Let me know if you would like the info to try.

    Andrew