Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Autologon issue with WMS 2012.

Answered Autologon issue with WMS 2012.

  • Friday, March 08, 2013 9:12 PM
     
      Has Code
    Sign In to Vote
    0

    I  am trying to set autologon on WMS2012 by updating following registry settings at 

    HKLM\Software\Microsoft\Windows NT\CurrentVersion\winlogon
    AutoAdminLogon = "1"
DefaultUserName = XYZ
DefaultPassword = password

    After reboot, WMS 2012 tries to  auto logon with "XYZ" user, but due to some issue it reboot the device then auto login using "WmsHost" username, do some initialization then log off to login UI.

    • Edited by DJ7115 Friday, March 08, 2013 9:22 PM
    •  
     

All Replies

  • Saturday, March 09, 2013 12:06 PM
     
     
    Sign In to Vote
    0

    What does Event Security log say?

    Hope you run regedit with elevated rights (Not sure if reboot is needed.)

    Regards

    Milos

     
  • Tuesday, March 12, 2013 7:05 AM
    Moderator
     
     
    Sign In to Vote
    1

    Hi DJ7115,


    Firstly, have you had this user account XYZ setup in your system? Is there any issue when logon the WMS 2012 with the account XYZ?


    Also, please check if this tool could help.


    Autologon for Windows v3.01

    http://technet.microsoft.com/en-us/sysinternals/bb963905.aspx


    Hope this helps.

    Jeremy Wu
    TechNet Community Support

     
  • Tuesday, March 12, 2013 9:18 PM
     
     
    Sign In to Vote
    0

    Gents,

    I am able to logon manually by XYZ account and i cant use external tool as i am having code which automates the autologon, internally it update the win registry. Event log doesnt speak anything about failure. I am highly doubting the security permission policies of Windows server 2012. anybody know how i can update security permission of system reg key, folder or files so that my application could access it.

     
  • Tuesday, March 12, 2013 10:29 PM
     
     
    Sign In to Vote
    0

    Following link explains about how to change ownership of object.

    http://superuser.com/questions/497095/how-to-delete-trustedinstaller-files-on-windows-8

    but still i am having issue.

     
  • Wednesday, March 13, 2013 5:07 AM
    Moderator
     
     
    Sign In to Vote
    1

    Hi,


    Thanks for the reply.


    However, what do you mean “update security permission of system reg key,     folder or files”? Would you please let us know more details. What do you want to achieve? What is the code doing?


    By the way, we do not recommend to modify permissions of system files due to it may make system unstable.


    Thanks.

    Jeremy Wu
    TechNet Community Support



     
  • Wednesday, March 13, 2013 2:48 PM
     
     
    Sign In to Vote
    0

    I'm not clear about a couple things in your explanations.

    What is the Wmshost account that, from your explanation, is used to login when you set it up for autologin for the XYZ account?  That is not a default Windows account, so it must be something you (or someone in your organization) added.

    Do you have any login/logoff scripts enabled in your environment?

    How is this an issue with Windows auto-login when you say you "cant use external tool as i am having code which automates the autologon".  Your explanation implies that you have something else that is trying to automate the process.

    I agree with Jeremy that we must be lacking some information about what you are trying to do.  An explanation of what you want to do instead of how you are trying to do it might be helpful, in addition to clearing up some of your other points.

    .:|:.:|:. tim

     
  • Wednesday, March 13, 2013 5:56 PM
     
      Has Code
    Sign In to Vote
    0

    Sorry for unclear update. We have had developed the system configuration application (which capable of perform Networking, user account, AD, virtual machine creation,virtual switch creation and sysprep etc activity ) to run on Hyper-V 2008 R2 core (Host) as well as Windows server 2008 R1 (VM). now moving forword we are migrating to Hyper-V 2012 (Host) and windows multipoint server 2012. most of functionality of our existing application works fine with Hyper-V 2012 and WMS2012, but i fails with following activity.

    Issue 1 - autologon setup on WMS2012:

    1. It succesfully update the win registry  "HKLM\Software\Microsoft\Windows NT\CurrentVersion\winlogon" for autologon XYZ user

    AutoAdminLogon = "1"
DefaultUserName = XYZ
DefaultPassword = password
    2. After reboot, device tries to get autologon using XYZ, but it automatically reboot the device then
    3. After reboot device gets autologon using "ComputerName/WmsShell" (Sorry for mentioning it as WmsHost in previous update). 
    4. Then it do some initialization, device get autolog off to login screen.  
    Issue 2 - Sysprep on WMS2012 :
    When tries to run sysprep activity using our application, which perform some our organization specific cleanup and then internally gives call to "C:\windows\system32\syprep\sysprep.exe". I get access denied error, even i am running application using local administrator user.
    Please let me know if any further information is required, Many thanks for your inputs...
     
  • Wednesday, March 13, 2013 11:00 PM
     
     
    Sign In to Vote
    0

    Still have some strange feelings about this ...

    "We have had developed the system configuration application"  Is this an application you have written and are having problems with or is it something you had someone else develop, and now you are trying to debug it?  From the way you worded the statement (have had developed), it sounds like you had a consultant write it.  You might want to go to the author of the application to see if they support it in a 2012 environment.  If so, they would hopefully be able to help you.

    autologon using "ComputerName/WmsShell"  WmsShell is not a standard Windows user name, either.  It sounds like this application that you had written is doing something strange.  The fact that this unknown user is getting autologged on when you have requested a different user account for autologon really makes me think that the application is making changes in areas it should not be.  Get the author to explain the exact process.

    As for the application running sysprep, are you sure the application is running under the logged in user, or is it using a service account?

    These two issues may or may not be related.  There are still a lot of unknowns about this 'application' that makes all these changes to your system.  It is really hard for anyone to provide much assistance without internal information about the 'application'.  If you can narrow it down to how the application is trying to do these things that are failing, it might (I stress the word 'might') help in helping discover root cause, but without more information about the workings of this application, a forum is going to be a difficult place to get assistance.  I really think you need to work with the application author to help narrow down where the problem is occurring.

    .:|:.:|:. tim

     
  • Thursday, March 14, 2013 2:39 PM
     
     
    Sign In to Vote
    0

    Tim,

    As per my understanding "WmsShell" is build in account from microsoft to support multi station mode. WMS stands for Windows Multipoint Server. Regarding our application  all want to say that the application is doing its job perfectly i.e. merging the registry (That's only thing application is doing for autologon, nothing else) . but after reboot system wipes out all registry changes made by application under winlongon. 

     

     
  • Thursday, March 14, 2013 4:48 PM
     
     Answered
    Sign In to Vote
    0

    Found solution autologon issue with WMS2012 by myself . we should disable to multipoint server host service. but still struggling with sysprep issue.


     
  • Thursday, March 14, 2013 6:43 PM
     
     
    Sign In to Vote
    0

    Ah!  Multipoint Server - that forum is here - http://social.technet.microsoft.com/Forums/en-US/windowsmultipointserver/threads

    As for the sysprep issue, more information is needed.  You simply state you are getting an access violation.  What is your 'application'?  Is it a program?  Is it just a script?  How is it trying to call sysprep?

    .:|:.:|:. tim

     
  • Friday, March 15, 2013 9:29 PM
     
     
    Sign In to Vote
    0

    Ok, found solution  by myself. It is bit complex to understand the root cause of issue. Folks if you are writing code for VM created from WMS2012 then you should understand WMS2012 VM it self is a host for various multipoint point stations or VM's. i.e. such kind of scenario will have 2 layer of virtualization.

    Hardaware -> Hyper-V 2012 ->WMS2012 (1st Layer of virtualization) -> Station or VM (2nd Layer of virtualization)

    So to run sysprep on VM (2nd layer of virtualization), the sysprep should be present at "C:\windows\syswow64\sysprep"

     

    • Marked As Answer by DJ7115 Friday, March 22, 2013 2:20 PM
    • Unmarked As Answer by DJ7115 Friday, March 22, 2013 2:20 PM
    •