Unable to login Windows Server 2012 after making local policy changes

Experts, we have modified the local policy setting on the windows server 2012 and badly it was domain controller now none of the users are able to login to the server. After entering the user name and password it will launch till welcome screen then it errors
out saying user name or password incorrect. below are the steps which we followed
1. Policy setting is located in Computer Configuration\Security Settings\Local Policies\Security Options \Network security: Configure encryption types allowed for Kerberos values change from Not Configured to DES_CBC_MD5
2. changed user attribute msDS-SupprtdEncryptionTypes to 2 , this account we were used for kerberos authentication. 
3. Logged off from the server and then server doesn't allow any user to login.
regards,
Jakk 

Have you tried connecting to the server from a 2nd DC? Have you tried installing the RSAT tools on a domain member server and modify the offending policy ?
last choice would be restart the DC into safe mode. 

Similar Messages

  • Unable to boot Windows Server 2012 after adding features (AD, DNS, DHCP)

    Hi,
    I'm installing a VM server 2012 and it installs without any problems. Able to boot it and login, I change the name of the server and restart it. Still no problem.
    Now when I want to add some features, Active Directory, DHCP and DNS, promoting to Domain Controller. Create a new forest and so on. When this is configured and installed the server wants to restart. It restarts but boots into a loop and ends up in System
    Recovery/Troublshoot. I have tried repairing the boot with bcdedit in cmd-prompt but not able to fix it. Same Issue in VMware and hyper-v manager on different hosts. Im thinking that the image is at fault, but its strange that everything works at the beginning. 
    Am I missing something? The image I'm using is from MSDN, Server 2012 debug checked with updates.  I'll try another image today, but why shouldnt that one work? 

    Hi Presaro,
    I’m glad to hear that everything is OK. Thank you for posting here.
    Best Regards,
    Tina

  • Issue with cisco acs 4.2.Users unable to login aaa client but after restarting group policy able to login

    issue with cisco acs 4.2.Users unable to login aaa client but after restarting group policy able to login

    issue with cisco acs 4.2.Users unable to login aaa client but after restarting group policy able to login

  • Unable to install Device CALs on Windows Server 2012 after OS Reinstall

    Due to a hardware fault we had to reinstall Windows Server 2012. I have activated the Terminal Services licensing Server but I am unable to install Device CALs that we have purchased.
    The error is as follows:
    "Remote Desktop Services Licensing is unable to process your request. Make sure you provided correct information. If the problem persists, try other methods of activation. Error code is 800"
    I tried contacting technical support over phone - they are also unable to resolve the issue.

    Hi, thanks for response.
    I contacted Clearing House over phone and provided them with all the details regarding authorization
    number(s), license number(s) et al. However they also mentioned that there is some technical error from their "tool" and directed me to Technet Forum.
    I shall try the Hotfix

  • Unable to Install Windows Server 2012 R2; system aborts and reboots after first blue Windows logo appears

    System:  Dell PowerEdge sc1420 with dual xeon and Adaptec 2420SA SATA RAID (supported by OS); 10 GB memory (2x4, rank 2, organization x4, in DIMM1 & DIMM2; 2x1, registered, organization x8, in DIMM3 & DIMM4)
    This computer is currently running Windows Server 2008 R2 Enterprise which was installed with no problems.
    Objective: clean install of Windows Server 2012 R2 Standard on an otherwise unused RAID array disk set.
    All attempts to boot from DVD result in loading of files (grey progress bar on bottom of screen), brief dark screen, then black screen with a blue windows logo for about 2 seconds and then a flash of about 10 lines of error notifications on a black screen
    for about 1/4 second (unreadable), and then a reboot of the computer.
    Coreinfo.exe confirms that cpus DO support NX and PAE; do NOT support VMX (virtual machine enhancements).
    Attempts to run memtest.exe from boot disk tool-menu startup result in an error message that the memtest.exe file is corrupt.
    Running memtest.exe from Windows 2008 R2 install disk results in all memory tests passed!
    Attempted booting with multiple DVD's (some +R, some -R, all verified) burned from .iso.  These DVD's were used successfully to install Windows Server 2012 R2 on an HP Pavilion.  Also changed DVD drives just to rule out DVD hardware. 
    Running CHKDSK from Windows 2012 R2 on HP Pavilion shows no problems; running CHKDSK from Windows 2008 R2 on the Dell system on the same disks shows some problems.  Running checkdisk on the Windows 2008 R2 install disk from the Windows 2008 R2 installed
    system shows no problems.  All disks burned and verified on same system.
    Also attempted to boot from USB thumbdrive with copy of DVD on it.  Same results: system loads files then reboots at first Windows logo.  So that would rule out disk quality issues per se??
    Started to try an upgrade rather clean install to see if any errors were announced.  None were announced as the system went through much of the process.  I aborted somewhere along the way before committing to the upgrade because 1) the most likely
    outcome was it would not boot after install (I don't really need the practice in restoring); and 2) even if it did reboot, having a system that can't be repaired by booting the install disk is pointless.
    All disks and raid arrays are recognized and usable by RAID controller card and by Windows Server 2008 R2.  Disks are within spec for use with Adaptec 2420SA (1TB @ 300).
    Is VMX (aka VT-x) actaully required for ANY install even though Hyper-V is not intended to be used?  If so, it is too bad that the Microsoft system requirements (
    http://technet.microsoft.com/en-us/library/dn303418.aspx ) don't make that clear.  And lack of VMX support really doesn't explain the memtest.exe "corruption" issue. 
    Or is it maybe something unique about the files on 2012 R2 disk (or disk image on USB) that are causing some problem with the chipset processing?  But why?
    My vote would be for the latter of the issues, but I have no clue why or if it is remediable.  Suggestions? 

    So here is what I think is the final understanding of this problem:
    First, one additional piece of important information:  The computer successfully moves into and through the Windows Boot Loader phase and succeeding phase ONLY for Windows 8.1 32-bit, but NOT for Windows 8.1 64-bit nor for Windows
    Server 2012 R2 (only 64-bit).
    The Windows Boot Manager phase (which precedes the Windows Boot Loader phase) is either 32-bit or 64-bit (64 –bit for this case) and is loaded by the 16-bit stub program (Bootmgr) which starts in real mode. 
    Windows Boot Loader of course runs in either 32-bit or 64-bit (64 –bit for this case) according to the product being installed.
    By inference, the essential problem is occurring in conjunction with the loading of a WIM file to start the Windows Boot Manager. 
    The boot manager starts ok and generally shows its essential screens (Windows Boot Manager; Advanced Boot Options) or proceeds to load files for transition into Windows startup in the succeeding Windows Boot Loader phase (that doesn’t “boot” but rather
    loads the system).  This is best confirmed by the announced corruption of the memtest.exe file when selecting Windows Memory Diagnostic from the Windows Boot Manager Screen. 
    If allowed to continue loading files to pass control to the Windows Boot Manager, the type of abort and resulting immediate restart that occurs is that which you would associate with unhandled cpu exceptions (invalid instruction, memory out of range,
    wild interrupt, etc.) that most of us have not commonly seen for 20 years (since beginning to use well behave OS’s from Windows NT 3.1 and on).
    So, the problem obviously is due to a failure to properly mount the WIM file and/or properly access it (probably the latter) when running in 64-bit protected mode. 
    This is independent of the hardware on which the install disk is actually mounted (DVD or USB-flash), so it is NOT a hardware problem
    per se.
    Since the WIM is mounted early in the process, Boot Manager may well have loaded it using BIOS routines to access the physical device on which it resides rather than loading 32-bit or 64-bit drivers of its own. 
    Hence, if the BIOS does not “mount” the WIM in a way that is later fully compatible with access from the 64-bit systems being loaded, it could cause apparent file corruption. 
    If it is only partially incompatible some functionality may appear quite usable (like loading files) until later detected. 
    This is vague on my part, because the exact nature of the incompatibility cannot be readily determined from the information available. 
    But the consequence is the same: the system cannot boot from the install disk, either for initial installation or repairs.
    Incidental conclusion:  The 64-bit boot manager code for Windows Server 2008 does not exhibit this faulty behavior, but the 64-bit code for Windows Server 2012 does. 
    So the problem is not inherent with loading 64-bit server OS’s.
    Expectations:  If the system were to be upgraded using the features of the install disk while running an installed OS, say Windows Server 2008 R2, it might well succeed and yield a fully functional system upgraded to Windows Server 2012
    R2 (because the installed operating system is started from discrete files, not from a WIM file). 
    However, in order to perform a disaster recovery using Windows resources (such as image backups from Windows Server Backup), one would have to presumably boot from a Windows Server 2012 64-bit install disk or Windows Server USB recovery drive. 
    Of course we know that the Windows Server install disk will not boot and we can be fairly sure that the problem will migrate to any Windows Server USB recovery drive that is created. 
    My inspection of a Windows 7 System Repair CD shows that is based exclusively on boot.wim, not discrete files! 
    Of course a generated image for a WIM for Windows 2012 USB recovery drive
    might not have the flaw that drives this behavior, but it probably would.
    Problem conclusion:  A BIOS upgrade would be required for compatibility with Windows Server 2014 clean installation
    and any maintenance; and none is available from the OEM.
    Problem not resolved, but understood for future reference.
    Thanks to Tim whose comments helped me focus my thinking.

  • Unable to activate windows server 2012 (0x80072F8F)

    I seem to be unable to activate my Windows Server 2012 Essentials. All I recieve is the following message:
    Windows couldn´t be activated
    Go to Control Panel to learn about other ways to activate
    Error code: 0x80072F8F
    Error description: A security error occurred
    This is a presisting problem and I can´t find any other way to activate in the control panel, what to do?

    I'd double check that the date / time are correct.
    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

  • Unable to Install Windows Server 2012 on Windows Server 2008 R2 SP1 Hyper-V

    My attempts to install are failing with a message "Windows cannot install required files. The file may be corrupt or missing....Error code: 0x800705070".
    I am posting this on the Wondows 2012 Server forum but I have had exactly the same problem as described below with Windows 2008 R2 SP1.
    As the title says this is on a Windows Server 2008 R2 SP1 host with all current updates. I have downloaded the ISO file from a Technet subscription file twice, once by direct download and once by the Akamai downloader. The virtual disk is connected with
    the default IDE driver. I mounted both installation images as ISOs, located on a file system on the host server.  I have tried installs by deleting the VM and recreating both the VM and a new virtual disk, re-using a previously created virtual disk, and
    deleting the partitions in a previously created virtual disk, and executing the format command, and then attempting the install.
    I have exactly the same problem trying to create a Windows Server 2008 R2 SP1 VM on the same host OS.  With those attempts, I downloaded the Technet subscription iso 4 or 5 times, and burned one to a DVD which I attached to the created VM.  Same
    error message.
    The virtual machines and virtual disks I created and used were all located on an RAID5 array, on a builtin Intel RAID controller using Intel Rapid Storage Technology software version 11.2.0.1066.  The host Windows Server 2008 R2 SP1 uses this file system
    but the OS is installed on a dedicated drive (C).
    I had previously created a guest VM with Windows Server 2008 R2 (several months worth of updates ago) without drama.
    I have spent hours reading forums and blog articles on this.  A common response is to download the iso another time, and/or burn it to a DVD instead of mounting an iso image. Although I didn't do the later yet with 2012 Server, but I have done these
    other steps attempting to install Windows 2008 Server SP1. The install process takes a while (not to mention doing multiple downloads). Given this seems to be a common recommended remedy, and indeed based on posts does seem to eliminate the problem is some
    cases, why doesn't somebody change the Microsoft installer program so it does a thorough integrity check at the beginning of the install process?

    Jeff,
    After the exercise of Windows 2012 Server successfully installing (as I described above) I also successfully installed Windows 2008 R2 on Hyper-V.  From my standpoint, I have eliminated the problem (which isn't the same as correcting the problem).
    The answer to your specific question regarding Hyper-V support is that the motherboard I am using, an Asus P5Q, is not supported by Windows 2008 R2 because it doesn't use ECC memory, and the vendor doesn't say it supports Windows 2008. But I am sure you
    know the motherboard vendors often don't test older motherboards with newer software versions.  It appears that in specifying ECC memory Microsoft is trying to protect users of Windows Server from hurting themselves, not saying the software won't run.
    Having said that, my suspicion in the beginning was, and still is, that it was some variable(s) left in an unknown state in the Hyper-V environment, which was why after trying to install Windows 2008 R2 several times I tried Windows 2012 which resulted in
    the same error, and then encountered the same error trying to install Windows 7 on the same Hyper-V installation. The specific Hyper-V Windows 2008 R2 server had run without any operating problems for months before I started having trouble, and although it
    had been quite a while since I had created VMs, that process used to work.  The hardware didn't change. What changed was applying updates through Microsoft Update, and a few access control rights I changed, and at least I think, I set back to their original
    value.
    So in short, no, my hardware isn't supported by Windows 2008 Server.  Two, your assertion that you are running the same software configuration that I am is very unlikely to be true. There are an extremely large number of things which are different between
    your test system and mine, such as which Windows 2008 components are installed, what updates were installed and in what order they were installed, and what other third party software each of us is running, and between AD, and all the features, a large number
    of potential differences in ACLs, options, etc. and I don't for a minute think this particular problem was caused by the underlying hardware.
    I do appreciate your taking the time to try to help me, and I hope there is one thing you and I could agree on. Microsoft could pretty easily make it much easier to isolate problems. In this day and age reporting hex error codes (as opposed to doing the
    table lookup in the error handling proc), and not providing more diagnostic information seems to me to be almost quaint.  And in this case Microsoft can dismiss my problems on the grounds it was all on unsupported hardware. Unfortunately, I think they
    are missing an opportunity to make their software better, because in my opinion what I encountered there are a set of conditions which will cause installations to fail that aren't going to get corrected.

  • Bank Screen when login windows Server 2012 R2 Standard

    Dear All,
    I open "Allow connection from computers running any version of Remote Desktop" in my tow Windows Servers 2012 R2 Standard.
    And I use Windows 7 RDC to connect to these two  Server.
    Sometimes, when I try to login the Windows (I can press "alt+ctl+del", input the password to login windows), I see a blank screen, it seems hang. but I also can "ping" or "telnet" the port from another server.
    There are same problem for these two servers.
    Because the screen is blank, I can not anything, One thing I can do is to reboot the server.
    anybody know how to solve this problem?
    Steven
    john

    There seems to be another post like this
    here
    If this is helpful please mark it so. Also if this solved your problem mark as answer.

  • Server admin is unable to login to server.app after upgrade to Mountain Lion Server?

    After upgrade to Mountain Lion Server I am unable to login to the server tools. When I input the admin user name and password the dialog box just shakes indicating the wrong password. But it is the correct password. How do I reset the password or if necessary how do I rest the server and start over on Mountain Lion. I found info on how to reset the server on previous versions of the server which involved executing a plist in the LaunchDaemon folder. However that file does not exist on the server following upgrade to Mountain Lion.
    Thanks, Howard

    I upgraded today and had the same issue. I took following steps to fix my computer.
    Boot into Recovery Partition (Hold Option Button while booting)
    Open Terminal.
    Type resetpassword
    Select your hard drive
    Select the user account (Administrator)
    Enter a new password for the user
    Reenter password
    Save
    Restart
    Boot normally, Login as Adminstrator with the new password and add "Admin" permission to your account.
    Restart
    Everything should be working as expected

  • Poweredge R730XD - unable to install Windows Server 2012 standard via DVD - limit progress via USB

    Hi all,
    hoping someone has encountered and sorted this problem.  I've had troubles installing W2012 on our newest batch of server - 4x R730XDs.  Either by deployment or booting directly by DVD I encounter the following message:
    "windows failed to start.  A recent hardware or software change might be the cause"
    So I wrote the iso for Windows to USB and booted off that which yielded this message:
    "We couldn’t create a new partition or locate an existing one. For more information, see the Setup log files."
    A colleague recognised the message and directed me these instructions:
    Start DISKPART.
    TypeLIST DISK and identify your SSD disk number (from 0 to n disks).
    Type SELECT DISK whatever disk number you have.
    Type CLEAN.
    Type CREATE PARTITION PRIMARY.
    Type ACTIVE.
    Type FORMAT FS=NTFS QUICK.
    Type ASSIGN.
    Type EXIT twice (one to get out of DiskPart, the other to exit the command line tool).
    It didn't work - the next and final message I have is:
    "An Operating System wasn't found.  Try disconnecting any drives that don't contain an operating system"
    As a last resort measure I pulled those disks out but no change to outcome.
    I've encountered these issues with 3 out 4 of the servers (I haven't bothered to install the 4th and last).
    To summarise the spec of the servers, R730XD - front drives fully populated with 24x 600GB SAS (currently not setup in an array) with additional 2x 300GB in a flex bay at the rear set to RAID1 for OS.
    Any suggestions or experiences appreciated.
    Kind regards,
    KCC

    Hi all,
    an update of sorts - we were able to progress futher by setting up a the RAID array for the boot drive inside of the Lifecycle controller (that aspect of LC I have avoided using for a few years due to lack of flexibility in creating multiple arrays).  Windows then installed as normal via deployment on 2 of 3 servers.  the third still exhibits the same issue.  We thought to perform a factory reset, if there such a thing, but am struggling to find such an option in the LC.

  • Can't login to Server app after hardware and hostname change

    I used Carbon Copy Cloner to completely clone a Mac mini Server onto another Mac mini Server. (The idea being that I can install and configure additional software just once and then easily set up identical servers by copying all hard drive contents.) This seemed to work great – the second Mac mini runs fine, including logins, networking etc.
    To avoid conflicts between the two servers, I changed the computer name in System Preferences/Sharing and ran:
    sudo scutil --set HostName someothername
    sudo changeip oldip newip
    The problem is that the Server app won't let me log in on the second Mac mini. It lists "This Mac" in the "Choose a Mac" dialog, but when I enter the correct username and password, login is refused (the login dialog is "shaken"). But the same login works for the operating system and SSH, and the account was definitely "allowed to administer this server". On the original Mac mini I cloned from, I can login with this account just fine.
    I even added the user account to the "Open Directory Administrators" group using ldapmodify on the command line, but that didn't help.
    Is it possible that there's something in the user directory that's bound to the hardware (maybe the Ethernet MAC address) or the hostname?
    Do you have any idea how I could fix this? I'm grateful for any help…

    this hasn't worked for me.
    When i follow the additional steps using terminal, the second command brings back the same outcome - 'David is not in the sudoers file. this incident will be reported'.
    I've been having trouble with login on for a week but didn't realise this was the problem. I've reset passwords, reinstalled OSX (twice) and now, bizarrely, i can log onto the mac mini as the administrator, but once logged in, the 'administrator' password doesnt work for anything. I can run Software Update because it comes up with a message:
    "Software Update wants to make changes. Type an administrator name and password to allow this".
    I then put in my password but it shakes and tells me its wrong.
    Can anyone advise any other solution? I'm kind of stuck - because the system doesn't recognise my admin password for updates, i cant update anything. And also because my itunes library was set up by a newwer version (I reinstalled OSX believing it would fix it reverting it back to a previous version) i can't listen to any music.

  • Windows Server 2012 Essentials - Implement Group Policy for the 1st time

    This is my first server. We have 15 users and 20 devices, all clients are running Win7 Pro.
    On the Dashboard, Devices tab, when I click on each device there is an option to implement Group Policy in the right-hand task pane. Does this mean I can implement it for one device at a time? Or will it happen for everyone in the domain?
    I'm hesitant to start. Is this something where I should wait for the weekend, so I can restore from a backup if need be?
    Thanks for your help
    Alan

    Time to get a basic Windows networking reference book and read up on group policy. Policies are applied by the system on a predicable refresh rate, which if memory servers is 15 minutes. This can be forced from the stations with the cli command "gpupdate
    /force" but in most cases there is little need to do so.
    Some, like folder redirection, only impact the stations on reboot/sign on
    Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit.

  • Unable to add File Server Resource Manager Tools on Windows Server 2012 - Errors on restart and roll back install

    Unable to install Windows Server 2012 Feature -  [Tools] File Server Resource Manager Tools.
    Installs, however when I restart the server error messages appears saying feature unable to install, windows reverting changes.
    In the Setup event logs have the following information message "Update FSRM-Infrastructure of package FSRM-All failed to be turned on. Status: 0x800f0922"
    Does anyone have any idea's on why this Feature can not be installed ??
    Scott

    Hi Shaun
    Tried both of your suggestions, however neither strategy worked.
    Strategy 1
    Tried installing via powershell - "install-windowsfeature -name fs-resource-manager -includemanagementtools"   
    Feature un-installed itself during the restart.
    Attempted to use the command "DISM /online /remove-feature /featurename:FSRM-Infrastructure-Services".  However
    this did work because one the Service was'nt installed or two because there was no command option for "/remove-feature"
    PACKAGE SERVICING COMMANDS:
      /Add-Package            - Adds packages to the image.
      /Remove-Package         - Removes packages from the image.
      /Enable-Feature         - Enables a specific feature in the image.
      /Disable-Feature        - Disables a specific feature in the image.
      /Get-Packages           - Displays information about all packages in the image.
      /Get-PackageInfo        - Displays information about a specific package.
      /Get-Features           - Displays information about all features in a package.
      /Get-FeatureInfo        - Displays information about a specific feature.
      /Cleanup-Image          - Performs cleanup and recovery operations on the image.
    Strategy 2
    Tried installing via powershell, using the following command DISM
    /online /enable-feature /featurename:FSRM-Infrastructure-Services, however got the same result, the install backed out during the restart.
    All up back to where I started?

  • In Place Upgrade WSUS windows 2008 R2 into windows server 2012

    Hi Team,
    i had question. I have windows server 2008 R2 and installed WSUS role at that server.
    Can I do inplace upgrade into windows server 2012 std edition?
    is there any impact into wsus services?
    thanks

    If it is not a DC, upgrade should be easy. And there shouldn’t be any problems.
    The question was about upgrading a WSUS server, and regardless of whether it's a DC or not, it most emphatically will not be problem free. In fact, it's flat out not possible! On WS2012 the upgrade will be blocked if WSUS v3 is present,
    and on WS2012R2 it will corrupt the WSUS installation beyond repair requiring a reinstallation of the operating system.
    Please review the
    WSUS v6 documentation regarding upgrade requirements.
    Warning
    Upgrade from any version of Windows Server that supports WSUS 3.2 to Windows Server® 2012 R2 requires that you first uninstall WSUS 3.2.
    In Windows Server 2012, upgrading from any version of Windows Server with WSUS 3.2 installed is blocked during the installation process if WSUS 3.2 is detected, and you are prompted to first uninstall Windows Server Update Services prior to upgrading Windows
    Server 2012.
    However, because of changes in Windows Server 2012 R2, when upgrading from any version of Windows Server and WSUS 3.2 to Windows Server 2012 R2, the installation is not blocked. Failure to uninstall WSUS 3.2 prior to performing a Windows Server 2012 R2 upgrade
    will cause the post installation tasks for WSUS in Windows Server 2012 R2 to fail. In this case, the only known corrective measure is to format the hard drive and reinstall Windows Server 2012 R2.
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • Windows Server 2012 R2 GPO Loginscript is executed with more than 2 minutes delay after login

    Hi everybody
    A strange problem came up in a new Windows Active Directory Domain (one single DC with Windows Server 2012 R2 Essentials): after configuring a User GPO with a Powershell Loginscript and applying the GPO to an User OU, the following happens:  when a
    User logs into a PC or Server, the Loginscript does not run within the first 120 - 150 seconds, and then suddenly the Scripts runs and completes within seconds. What could be the reason for such a long delay?
    When I run the Powershell Script manually it runs immediately and finishes within seconds. But assigned through a GPO it takes really long to run. I also tried a very "simple" Loginscript with only one command (map a network share) - but this Script
    also runs with a long delay. So the script does not seem to be the problem but the Logon Procedure. I even tried the same script with a locally defined GPO on a Windows Server 2012 R2 (just to check whether it might be a NETLOGON/SYSVOL share problem), but
    no luck - it takes 2 to 3 minutes until the Script is run. I went a bit further and realized that the problem is only related to the latest OS Windows 8 (8.1) / Windows Server 2012 (R2) but not to older windows system. So what changed in the logon process
    of the new Windows versions? Why are GPO applied with a such a long delay?
    Any ideas?
    Mark

    Other people have reported similar issues
    http://www.edugeek.net/forums/windows-8/128421-group-policy-logon-scripts-delayed-5-minutes-windows-8-1-design.html
    Rgds
    Milos

Maybe you are looking for