Windows 2008 R2 DC VM's hang at start-up

I have 2 Virtual Domain Controllers, they login fine for about 4 weeks after a reboot.  After about 4 weeks when logging in via Remote Desktop then they stay at the welcome screen, or they hang at the Group Policy phase of the log in.
Now I have one that hung on the Group Policy phase of the Log out.  
I've tried a lot of fixes I've found on this site, and others on the internet.
Any ideas why this could happen?

Hi Josh,
Is the group policy “Always wait for the network at computer startup and logon” enabled? If yes, please disable it to see if the issue persists.
This group policy is under Computer Configuration\Administrative Templates\System\Logon.
More information for you:
Control How Group Policy Is Applied At Logon
http://technet.microsoft.com/en-us/magazine/gg486839.aspx
Best Regards,
Amy

Similar Messages

  • Windows 2008 R2 - Error 2 Server Service wont start

    He
    We tried to start the Server Service on windows 2008 R2 but it wont start error: 2. While we check the service dependency we are unable to see the "SMB 1 xxx Driver" instead it is having name SRV.
    so how to restore the service back to the original state please let us know.

    Hi SPV4645,
    The following similar thread solution may work for your case.
    Server service (lanmanserver) will not start
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/3316a5e0-fc2f-4300-917d-66e1527b4aa7/server-service-lanmanserver-will-not-start
    Please also confirm the File and Printer Sharing for Microsoft Network driver has selected.
    The related KB:
    You receive a "The server service is not started" error message when you try to add a user to a group in Windows XP
    http://support.microsoft.com/en-us/kb/885859
    I’m glad to be of help to you!
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • OBI EE 11.1.1.7 on windows 2008 R2 - weblogic admin server don't start

     

    Sorry...the installation was successful, the services started as I could verify in weblogic console, em and BI presentation front-end.
    But when I shutted down, then weblogic didn't start anymore with the following error:
    <24-apr-2013 15.48.12 CEST> <Error> <DiagnosticsInstrumentor> <BEA-320800> <Fail
    ed to cache instrumentation engine configuration at C:\BI\user_projects\domains\
    bifoundation_domain\servers\AdminServer\cache\diagnostics\InstrumentationEngineC
    onfig.ser with exception java.io.FileNotFoundException: C:\BI\user_projects\doma
    ins\bifoundation_domain\servers\AdminServer\cache\diagnostics\InstrumentationEng
    ineConfig.ser (Access is denied)
    java.io.FileNotFoundException: C:\BI\user_projects\domains\bifoundation_domain\s
    ervers\AdminServer\cache\diagnostics\InstrumentationEngineConfig.ser (Access is
    denied)
    at java.io.FileOutputStream.open(Native Method)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:194)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:145)
    at weblogic.diagnostics.instrumentation.engine.InstrumentationEngineConf
    iguration.saveEngineConfiguration(InstrumentationEngineConfiguration.java:281)
    at weblogic.diagnostics.instrumentation.engine.InstrumentationEngineConf
    iguration.getInstrumentationEngineConfiguration(InstrumentationEngineConfigurati
    on.java:229)
    at weblogic.diagnostics.instrumentation.engine.InstrumentationEngineConf
    iguration.getInstrumentationEngineConfiguration(InstrumentationEngineConfigurati
    on.java:204)
    at weblogic.diagnostics.instrumentation.InstrumentationLibrary.loadInstr
    umentationEngineConfiguration(InstrumentationLibrary.java:180)
    at weblogic.diagnostics.instrumentation.InstrumentationLibrary.getInstru
    mentationLibrary(InstrumentationLibrary.java:121)
    at weblogic.diagnostics.instrumentation.InstrumentationManager.getAvaila
    bleMonitors(InstrumentationManager.java:315)
    at weblogic.diagnostics.instrumentation.InstrumentationManager.<init>(In
    strumentationManager.java:122)
    at weblogic.diagnostics.instrumentation.InstrumentationManager.getInstru
    mentationManager(InstrumentationManager.java:185)
    at weblogic.diagnostics.instrumentation.rtsupport.InstrumentationSupport
    Impl.getMonitor(InstrumentationSupportImpl.java:77)
    at weblogic.diagnostics.instrumentation.InstrumentationSupport.getMonito
    r(InstrumentationSupport.java:371)
    at weblogic.servlet.internal.ServletRequestImpl.<clinit>(ServletRequestI
    mpl.java)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:169)
    at weblogic.kernel.FinalThreadLocalList.initialize(FinalThreadLocalList.
    java:44)
    at weblogic.t3.srvr.PreConfigBootService.start(PreConfigBootService.java
    :70)
    at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesMan
    ager.java:461)
    at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServ
    icesManager.java:166)
    at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
    at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
    at weblogic.Server.main(Server.java:71)
    >
    <24-apr-2013 15.48.13 CEST> <Critical> <WebLogicServer> <BEA-000362> <Server fai
    led. Reason:
    There are 1 nested errors:
    weblogic.management.ManagementException: Unable to obtain lock on C:\BI\user_pro
    jects\domains\bifoundation_domain\servers\AdminServer\tmp\AdminServer.lok. Serve
    r may already be running
    at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.ja
    va:206)
    at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.ja
    va:67)
    I saw that may there could be some problem related to the UAC of windows....coult it be?
    Micaela
    Edited by: 1002579 on 26-apr-2013 1.35

  • MMC hangs on Windows 2008 and SAP MMC console not coming up

    Hi All,
    We are running SAP CRM 7. After upgrading Windows 2003 to Windows 2008 R2, SAP is coming up on our J2ee engine. We are able to login to the SAP J2ee application, but SAP MMC hangs. After the reboot, SAP MMC does come up but it hangs while starting the SAP Server Processes. We have to close the MMC from CTRL-ALT-DEL (end process). After that SAP MMC does not come up. Although, we can number number of MMC.EXE running in task manager,but
    the SAP MMC window is not displayed.
    We have gone through OSS note Note 1326097 - SAP MMC Snap-In crash for certain operations and installed the new version of MMC. But still the error exists. Also, we have installed the VCREDLIST patch and have installed all the DLLs mentioned in OSS SS Note 684106 - Microsoft runtime DLLs.
    Also, the event viewer shows the following message
    Log Name: Application
    Source: Application Hang
    Date: 9/9/2011 8:32:30 AM
    Event ID: 1002
    Task Category: (101)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: sap-xp-q01.com
    Description:
    The program mmc.exe version 6.1.7600.16385 stopped interacting with
    Windows and was closed. To see if more information about the problem is
    available, check the problem history in the Action Center control panel. Process ID: fcc
    Start Time: 01cc6f03c402c248
    Termination Time: 6
    Application Path: C:\Windows\system32\mmc.exe
    Report Id: e74f009f-daf8-11e0-afd2-000c29701b8a
    Also, we have upgraded the SAP Kernel to the latest patch level and installed MMC latest patch.
    Please suggest.
    Thanks,
    Antarpreet

    Hello,
    Try to re-create (re-register) the SAP Services (SAP instance services) in services.msc list. Then try to put SAP MMC up.
    Or, after recreation of sap instance services, try to reconfigure the sap mmc as well -
    http://help.sap.com/saphelp_nwpi71/helpdata/en/49/0eb43799b4740ee10000000a421937/content.htm
    Thanks

  • Windows 2008 standard hangs during chkdsk

    I have a file share server running windows 2008 standard edition.  It is connected to a SAN via Fiber channel.  There are 4 volumes presented to the Server via the SAN.  After a critical error occured, I restarted the server and the OS requested
    that I run chkdsk on the SAN volumes.  I allowed it to run.  It quickly got to the indexs, but then got hung at about 49% in stage 2.  After letting it set for several hours, I was forced to hard boot.  Upon restart, I did not allow the
    chkdsk to run as this is a production server.  The server booted up with no issues and all of the data was intact.  I recently migrated the data via Thin Import to a new SAN.  All of my data now resides on a brand new set of discs in my compellent
    array.  To save down time, I presented the volumes to the server using the same drive letters.  The server immediatly asks to run chkdsk on these volumes.  I run chkdsk and it still hangs in the same spot on the indexes.  I've made snapshots
    of the volumes and presented those to another server.  After running a rescan in disk managment, that server requests a scan and fix.  I let that run and it completes.  I'm at a loss on how to correct this issue.  The data seems fine, but
    chkdsk will not complete.

    Hi,
    Stage 2: Chkdsk checks the directories in the volume. Based on your description, please use
    chkdsk /x command to force the volume to dismount. Then check if you can execute the process of chkdsk successfully.
    Meanwhile, please go to Event Viewer and check if you can find some related errors.
    Hope this helps.
    Best regards,
    Justin Gu

  • Upgrade of Integation Services (Windows 2012 R2) on Windows 2008 R2 with Exchange 2013 SP1 DAG fails

    Here is the scenario:
    Legacy Host: Windows 2008 R2
    Guest VM: Windows 2008 R2 with Exchange 2013 SP1 DAG cluster.
    After importing the VM (2008 R2 and Exchange 2013 DAG) into a 2012 R2 host (Cluster).  (copy VM files to new 2012 R2host) Everything works fine.
    Then upgrading "Installation Services" (for Windows 2012 R2 host) on the imported VM runs fine with no errors to the "Restart" prompt. VM than shows: "Configuring Windows updates 32% complete. Do not turn
    of your computer." Hangs there for about 20 minutes until is says "shutting down". Hangs there for 20 minutes until power off. Restart to normal start; "Preparing to configure Windows. Do not turnoff your computer." proceeds slowly
    to "Configuring Windows updates 32% complete. Do not turn of your computer." hangs there again indefinite. Sometime hangs at shutdown cycle and "Configuring Windows updates 32% complete. Do not turn of your computer." indefinitely.
    I moved 20 other machines from a 2008 R2 host to new Windows 2012 R2 hosts all of these machines install the 2012 R2 Integration services just fine on the 2008 R2 VM. Just the 2008 R2 VMs clustered (DAG) and Exchange 2013 SP1 do not take the Integration
    Services upgrade.
    Any advise from Microsoft? I know I could decommission the DAG and Exchange machines and install Integration services on the native box before Exchange and DAG and that would sure work, but I'd rather avoid that amount of work for a simple integration layer
    upgrade.
    Thanks
    Gerhard Waterkamp ACSLA Inc.

    Hi,
    Could you try use the following method to fix this issue first?
    1. Run the System Update Readiness Tool, then check if there is any error in the Checksur.log and checksur.persist.log.
     1. Please run the System Update Readiness Tool on this affected server. Please download this tool from the following Microsoft article:
     Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, and for Windows 7
     http://support.microsoft.com/kb/947821/en-us
    2. The System Update Readiness Tool creates the log files that captures any issues that the tool found or fixed. The log files are located at the following location:
    %SYSTEMROOT%\Logs\CBS\
    3. Please paste the checksur.log here for analysis.
    If there is no error found, please try the following step.
    ==================================
    2. Use Fix it tool to reset the Windows Update components.
     1. Open the following link.
     http://support.microsoft.com/kb/971058/en-nz
     2. Select Windows 8.1, Windows 8 and Windows 7 in the product selection box.
     3. Click “Run Now” to reset the Windows Update components.
    Note: We can reset the Windows Updates manually by following the steps in the KB above.
    3. Use the System File Checker tool to repair missing or corrupted system files
     1. Open the command promote with Administrators.
     2. At the command prompt, type the following command, and then press ENTER:
         sfc /scannow
    Any errors are found in the steps above, please let me know.
    Hope this helpful.
    Best Regards,
    Jason Zeng
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Windows 2008 Server R2 & SAP Business One

    Does anyone have any experience, good or bad, with SAP Business One and Terminal Service on Windows 2008 Server R2?  We are finding a number of issues with this configuration and we are looking for any feedback that is out there.
    Here is the situation - our customer is running SAP Business One v2007 SP01 PL09 Hotfix4 on a Windows 2008 Server R2 machine.  All users (15 max) access SBO via Terminal Service to this machine, which also holds the databases (SQL Server 2005).  The machine currently has 20GB of RAM.
    What we are finding is:
    1) When any process related to SBO (SBO core or add-ons) consumes some portion of memory, none of that memory is ever released back to the O/S until SBO is completely closed.  So over the course of a day each user ends up simply consuming more and more memory as forms are opened for transactions.  While we do see this in Windows 2003 Server to some extent, at least some memory is released when a given form is closed.
    2) Once the system hits a point where around 75% of RAM is consumed the users start seeing application "hangs" and are forced to manually terminate SBO (via Task Manager) and restart.  There doesn't seem to be any paging or use of virtual memory (if my terms are right) in use.
    3) If the system is busy and a new window/form is opened the new window immediately (within one or two seconds) presents the "Not Responding" message on the new window.  Depending on the circumstances the application is simply waiting for resources and will continue opening normally.
    I would appreciate feedback from anyone who has experience with Windows 2008 Server R2; and especially using it for Terminal Services.  My personal feeling is that it is a platform that should be avoided but we would certainly like to hear what other folks have to say.
    Regards,
    Ross Unger
    Third Wave Business Systems

    I believe the supporting of this OS is still on Planned basis.  You may check with SAP support to give them a good user case to fight with any non-compatible issues.
    Thanks,
    Gordon

  • "BCP Commit Failed" New Install On Windows 2008 R2 with SQL Server 2008 R2

    I am installing a new Netweaver install on a virtual machine loaded with Windows 2008 R2 and SQL Server 2008 R2. The install gets to the "Import ABAP" phase and just hangs. SAPINST says it is still running, but there is no activity to suggest there is anything going on. There are no errors in the main logs, but after digging a little I did find these errors in the SAPSDIC.log file.
    (IMP) INFO: EndFastLoad failed with <2: BCP commit failed:[Microsoft][SQL Server Native Client 10.0][SQL Server]Violation of PRIMARY KEY constraint 'BADI_CHAR_COND~0'.>
    (IMP) ERROR: EndFastload: rc = 2
    (DB) INFO: BADI_FILTER created
    (DB) INFO: BADI_FILTER~0 created
    (IMP) INFO: EndFastLoad failed with <2: BCP commit failed:[Microsoft][SQL Server Native Client 10.0][SQL Server]Violation of PRIMARY KEY constraint 'BADI_FILTER~0'. Ca>
    (IMP) ERROR: EndFastload: rc = 2
    (DB) INFO: BADI_IMPL created
    (DB) INFO: BADI_IMPL~0 created
    (IMP) INFO: EndFastLoad failed with <2: BCP commit failed:[Microsoft][SQL Server Native Client 10.0][SQL Server]Violation of PRIMARY KEY constraint 'BADI_IMPL~0'. Cann>
    (IMP) ERROR: EndFastload: rc = 2
    Anyone have any ideas as to what might be going on? I can't find anyone with this exact same error. And this is our first attempt at installing a system with Windows 2008 R2 and SQL Server 2008 R2. All of our other Windows SAP systems are on Windows 2003 and SQL Server 2005 and we're in the process of upgrading - this being the first system.
    Thanks in advance,
    Michael

    Set BCP_LOB=1 in your system environment
    Note 1156361 - R3load: Fastload doesn't support LOB-columns
    Markus

  • Can't install 64-bit DAC on Windows 2008 R2 64-bit

    Hi all,
    When I attempt to run the 64-bit DAC setup.exe installer (either from the root folder or from win64), I get the following:
    Checking swap space: must be greater than 150 MB . Actual 3319 MB Passed
    Checking monitor: must be configured to display at least 256 colors Higher than 256 . Actual 65536 Passed
    Preparing to launch Oracle Universal Installer from D:\temp\OraInstall2011-08-2_03-11-12PM. Please wait ...
    checkdir error: cannot create D:/temp/OraInstall2011-08-2_03-11-12PM/jdk/
    unable to process jdk//COPYRIGHT.
    checkdir error: cannot create D:/temp/OraInstall2011-08-2_03-11-12PM/jdk/
    unable to process jdk//LICENSE.
    checkdir error: cannot create D:/temp/OraInstall2011-08-2_03-11-12PM/jdk/
    unable to process jdk//LICENSE.rtf.
    checkdir error: cannot create D:/temp/OraInstall2011-08-2_03-11-12PM/jdk/
    unable to process jdk//README.html.
    checkdir error: cannot create D:/temp/OraInstall2011-08-2_03-11-12PM/jdk/
    unable to process jdk//README_ja.html.
    checkdir error: cannot create D:/temp/OraInstall2011-08-2_03-11-12PM/jdk/
    unable to process jdk//README_zh_CN.html.
    checkdir error: cannot create D:/temp/OraInstall2011-08-2_03-11-12PM/jdk/
    unable to process jdk//THIRDPARTYLICENSEREADME.txt.
    I've tried to download the ZIP file a number of times and I've tried this on a number of Windows 2008 R2 64-bit machines, all with the same result. I'm able to run the 32-bit installer without error.
    There's a similar post already on here that suggests using compatibility mode but nothing I've tried has enabled me to install 64-bit DAC on a 64-bit Windows 2008 R2 machine.
    Has anyone successfully achieved this?
    Thanks!
    mroshaw

    Doc Id: ID 849658.1
    Alert : DAC 10.1.3.4.1 64-bit universal installer fails/hangs on Windows 64-bit and Linux 64-bit
    "The issue is 32-bit OUI installer is used for all DAC 10.1.3.4.1 installation which fails during verification/checks on 64-bit machine. It's Installer check which fails, DAC files are fine for 64-bit OS."

  • Windows 2008 R2 Failover Cluster - Netapp FAS6280 Black Screen on Restart when in cluster IGROUP

    Hello everyone,
    I've been working on this issue for a month now and have tickets open with Netapp and Microsoft.  We have not been able to resolve the issue as of yet and since I'm losing all my hair I thought I should post it...
    Scenario:
    Two Windows 2008 R2 Enterprise SP Fail-Over Clusters (C1 & C2)
    Two Netapp FAS6280 Filers for SAN storage
    8 DELL R815 servers w/ 2x QLE2562 8GB FC HBAs all paths used (9.1.9.47 - newer did not resolve)
    Netapp DSM 4.0 & SnapManager 6.4.2 (we also tried 1 rev newer, 1 rev older without luck)
    C1 has 2 nodes & C2 has 4 nodes.
    We are trying to add new nodes into the clusters.  We were originally on EMC Clariion arrays and have been migrated to the netapp.  Prior to moving we had 3 nodes in C2 and added node 4.
    Now we want to add 2 more nodes, one to each cluster.  We were able to configure the OS and get everything installed and matching the other nodes.  we can assign HBAs to a test IGROUP and assign a lun, format it use it restart all is well and normal. 
    As soon as we change the HBAs to the IGROUP for C1 or C2's LUNs the servers don't want to restart properly.  They hang at a black screen.  The little green windows start splash screen runs the bar at the bottom.  it then is supposed to fade
    out and come back with the grey screen saying starting windows but that doesn't always happen.  Sometimes it can take 4 hours to restart, or the machine will not come back onine at all.  The pre-existing nodes *do not* experience this issue. 
    They restart in 5-10 minutes without issue.
    We know drivers are part of the issue, but the maddening part is that it all works fine until we try to add the HBAs to the existing cluster storage group.  We have a suggestion to create separate IGROUPs for each cluster node and add all luns to the
    separate igroups.  We configured this on one node and it still restarts long.  We plan to modify the other nodes during our maintenance window and try again.
    On the other cluster we were able to successfully complete the validate wizard and join.  everything fails over and works except the server does not come up upon restart.  If I unplug the HBAs it will come up fine, then I can plug them in and the
    cluster functions.
    Does anyone have any other ideas for us to try?  Currently support for both netapp and Microsoft appear stumped.  Sunday is our Window and we plan to try reconfiguring but I'm losing optimism...
    Thanks for any feedback/ideas!
    -Ryan

    Thanks everyone who looked at this and offered feedback.
    The issue appears to be resolved after the configuration change suggested by Netapp support. 
    The originally recommended configuration for our storage migration was similar to how I've seen storage groups configured on EMC arrays in the past.  1 storage group / igroup with all hbas/initiators for each host in the WFC/SQL cluster added to this
    group.  that group then gets all LUNs assigned to it. 
    The change in configuration that was recommended is to have 1 storage group / igroup for each host and put all initiators/hbas for each host in their own separate group.  Then assign the all LUNs to each of the individual host igroups. 
    There is a lack of documentation on this, but it appears to work.  We had 1 hit for separate igroups but had to go through a couple of support techs to get one to confirm this.
    After applying this configuration in our change window today the issue is resolved.  we were able to fail all resources onto the new node and restart it without issue.  The question remaining for us is why the old systems continued to work while
    the new nodes did not.  The old nodes were originally migrated off an EMC and the version of ONTapp at that time was 8.1.2 and they worked fine.
    We had upgraded to 8.1.3 to resolve an issue with flash cache and it seems like machines that we tried to attach to this igroup after that time did not work.  all drivers software etc the same.  We are wondering if this is somehow related and have
    asked about it.
    I wanted to update this thread, and perhaps it can save someone else some trouble down the line.
    -Ryan

  • How to reduce size of C:\Windows\winsxs folder in windows 2008 R2?

    Hello,
    Is there any way to reduce size of C:\Windows\winsxs folder in windows 2008 R2
    simular to 
    DISM /online /Cleanup-Image /SpSuperseded
    Many thanks

    Okay maybe some background on the root of the problem would help.
    Windows XP (and Windows 2000) used a fast and great mechanism called Hotfix Installer (Update.exe) to install updates. Updates installed in very little time. If you wanted to further reduce update times on Windows XP, you could just temporarily stop the
    System Restore service and updates would install at crazy speeds. Note that this is not recommended for novice users who don't know advanced recovery methods, as some updates can sometimes cause your system to stop booting so you cannot even uninstall them.
    The method the Hotfix Installer used was simple, it just installed a new version of files to be updated at %windir%\system32 and %windir%\system32\dllcache (the Windows File Protection cache). For files that were in use, a restart copied them from dllcache
    to the system32 folder. This is simple file-based servicing. The hotfix installer (Update.exe) also supported various command line switches like /nobackup which means not to backup files it patches. Again, this is not recommended for novice users as some updates
    can screw your system even after the comprehensive testing Microsoft does before releasing them. But if you won't be uninstalling any updates (usually one only requires uninstalling updates if they cause problems), you could save a ton of disk space by not
    backing up the files it patched. The Hotfix Installer backed up files to C:\Windows\$Uninstall$KBxxxxxx folders so even if you did back up the files at install time, they could be safely deleted after a few days if no stability issues were found after using
    Windows with the newest updates applied. Update.exe also supported the very important and convenient ability to slipstream a service pack or update into the original Windows setup files using the /s switch.    
    When Microsoft was developing Windows Vista, they realized that components had gotten too many interdepencies on each other and to service each file reliably without breaking another component that relied on it, Microsoft introduced what they called as Component
    Based Servicing (CBS). You can read all about it in a much more technical way at The Servicing Guy's blog. What CBS does basically is it installs all files of the entire operating system, including all languages into C:\Windows\WinSxS and then it hard-links
    files from there to C:\Windows\system32. This has the benefit of not having to insert the OS disc to add or remove any components, and some other advantages as well like offline servicing of a Windows Vista or Windows 7 image. But the design introduces a major
    disadvantage of taking up a lot of hard disk space. Whenever an update is installed, it no longer installs it to C:\Windows\system32 and C:\Windows\system32\dllcache like Windows XP's hotfix installer (Update.exe) did. Instead, it updates the files in C:\Windows\WinSxS.
    Now, Windows keeps multiple copies of the same file but with different version in WinSxS if it is used by more than one Windows component. The higher the number of components, that many number of times the file exists in C:\Windows\WinSxS. When a Windows Vista
    update (.MSU) is installed, the components get updated, each and every one, instead of the files and the worst part is it still maintains the older superseded previous versions of components in WinSxS so the user would be able to uninstall updates. Microsoft
    does say that some sort of "scavenging" or deleting older copies of components takes place but is scarce on the details. The scavenging seems to take place automatically at certain intervals in Windows 7 but not in Windows Vista. In Windows Vista, you have
    to add or remove any Windows component for the scavenging to take place. And Microsoft says the scavenging will free up some disk space but in practice, on my system, I see my free disk space only decreasing on Vista as I remove or add any component. Windows
    does not give the user an option to not backup the earlier versions of components like Windows XP's /nobackup switch in Hotfix Installer did. As as you install more and more updates on your system, they will take more and more disk space. This is one of the
    primary reasons Windows Vista and Windows 7 are so bloated. Another reason for them being so bloated is the DriverStore that these OSes store. All drivers that are shipped with the OS and the OEM ones which you download and which are installed for a particular
    system are staged in C:\Windows\System32\DriverStore. But let's not go there for now.
    Now, an important thing to note is that the size of the WinSxS folder is not what Explorer or the dir command report, it is far less but is misreported by Explorer because it counts the hard links more than once when calculating size. That does not mean,
    the size of WinSxS is not causing real-world disk space problems on numerous Windows Vista/7 systems in use today. Microsoft's ingenious recommendation to this problem of ever growing disk consumption is to install fewer updates to keep the size of the servicing
    store under control. Of course, users cannot deny installing security updates and leave their system open to security holes. What they can do is install less optional updates, the ones that Microsoft releases on the fourth Tuesday of every month and also install
    less of the hotfixes that are available by request from a Knowledge Base article. In short, you have to trade the number of bugs fixed in the OS by installing hotfixes at the cost of enormous amounts of disk space. The whole servicing stack is a total downgrade
    to Windows XP's update.exe method. It causes heavy disk thrashing and slow logoffs/logons while Windows configures these updates at the Welcome Screen. Many systems are unable to boot because of failed updates. Another disadvantage of the "new" servicing stack
    (and the redesigned Setup mechanism of Windows Vista) is the inability to do a true slipstream of service packs and hotfixes.
    The time it takes to actually install these hotfixes online compared to Windows XP is also completely unacceptable. When you start installing an MSU update, it spends a lot of time determining whether the update applies to your system. Then, the update itself
    takes much longer to install compared to Windows XP's Update.exe (hours instead of minutes if you are installing dozens of updates through a script). Finally, that post-installation process ("Configuring updates... Do not turn off your computer") takes several
    minutes before shut down followed by a second post-installation process (configuration) upon restart before logon that also takes also several minutes and thrashes the disk.
    I can install the entire SP3 for Windows XP in about 10 minutes after downloading the full installer. I can also install a slipstreamed-with-SP3 copy of Windows XP is about 45 minutes on a modern fast PC. In contrast, Windows Vista or Windows 7 do install
    relatively quickly (in just about 15-20 minutes) on a modern PC but installing the service packs and updates takes more time than anything on XP did. Not only can service packs not be slipstreamed, but Vista Service Packs are not even cumulative, which means
    if you clean install Windows Vista today, you have to install SP1 first which takes about 90 minutes, then SP2 which takes less time, then all the post-SP2 updates which do take hours to install. If you really HAVE to use Windows 7 or Windows Vista, you are
    stuck with this slow update non-sense as Microsoft does not even acknowledge that there is any slowdown or loss of functionality in the new servicing mechanism. The fact remains: MSU updates are slow as **** and take too much time and as Windows 7/Vista get
    older and Microsoft stops producing service packs, a clean install is going to take longer and longer to bring it up-to-date with all patches installed. Is is worth wasting your time on an OS whose servicing mechanism Microsoft completely screwed up? I once
    again recommend you read more about the servicing stack and how it operates at The Servicing Guy's blog:http://blogs.technet.com/b/joscon/. To fix this messed up servicing stack, Microsoft also offers a tool
    called CheckSUR for your system if it finds “inconsistencies in the servicing store”.
    Microsoft's Windows Vista and Windows 7 products are not engineered with disk space in mind. It causes a problem, especially for SSDs which are still low capacity and very expensive. The only hope is that Microsoft again completely redesigns this servicing
    mechanism in a future Windows release so it would not cause this growing disk space consumption issue, speed up installation of updates by an order of magnitude, not slow down logon and logoff, not prevent systems becoming unusable because of failed updates
    being stuck at a particular stage and allow true slipstreaming.
    Microsoft's response to this is vague - they simply state "Windows 7's servicing is more reliable than Windows XP" but they cannot acknowledge it is a million times slower and still unreliable...slow to the point of being unusable and sometimes leaving systems
    in an unbootable damaged state. Of course they know all this too but can't admit it since it makes their latest OSes look poor. Moving from a very simple and fast update mechanism that worked to a complex one that requires endless “configuring” and repair
    through CheckSUR is a product engineering defect.
    Take a look at servicing-related complaints in Microsoft's own forums:
    1.
    Very slow install of updates to Windows 7
    2.
    Windows 7 - Updates are very slow
    3.
    Windows 7 Ultimate, it takes long time configuring updates
    4.
    "Preparing To Configure Windows. Please Do Not Turn Off Your Computer"
    5.
    Very slow update install at shutdown (Windows 7 Home Premium)
    6.
    Why does my computer run so slow when installing updates?
    7.
    Every time the computer is shut down, it always says installing update do not turn off your computer
    8.
    Computer is working slow and wants to do windows updates all the time
    9.
    Windows 7 Update install time taking a very long time
    10.
    Windows wants to install 6 updates every time I log off or put the computer in sleep mode
    11.
    Problem In Configuring Windows Updates at the time of Startup
    12.
    Computer really slow after latest updates
    13.
    Windows hangs up in "configuring updates"
    14.
    Why can't windows 7 install updates?
    15.
    Every time computer is shut down, receive Installing updates, do not shut off....
    16.
    How long does it take for the Windows 7 Home Premium updates take?
    17.
    Windows 7 "Installing Update 2 of 2" for 12 hours now
    18.
    Updates causes endless reboots
    19.
    Updates stuck installing for over 24 hrs. Computer does not boot
    20.
    Cannot load Windows 7 after installing 2 critical updates
    A proper solution to this problem would be to completely re-engineer and rewrite the servicing mechanism so it operates with the speed, reliability and pain-free operation of the XP servicing mechanism.
    I don't see this situation improving in Windows 8 either. Good luck with your Windows tablet taking hours to install service packs and updates. Now, do iPads take that long to install updates?
    Microsoft understated the real system requirements to keep a Windows 7/Vista system running. System requirements at install time may be 15 GB of free disk space but over time, this number increases to alarming levels as you install more service packs and
    post SP-updates. You can find out the real size of the WinSxS folder using a tool like cttruesize (ctts.exe) (download it from
    http://www.heise.de/software/download/cttruesize/50272 and run ctts -la -a -l C:\Windows to find the correct size minus the hard links which MS says causes Explorer to misreport the WinSxS
    folder size but the fact remains that even with the correctly calculated size of WinSxS, the disk space requirements of Windows 7 to keep it updated are unacceptable, especially for people's SSDs which are running out of disk space!

  • Not Able To Assign A Static IP Address To Windows 2008 64 bit Server

    Hello Experts,
    I've been trying to assign a static IP address to Windows 2008 R2 Server Virtual Box image. As soon as I assign static IP address to the image, either it hangs or says "Unidentified network".
    I'm 100% sure that I'm using correct IP address, Gateway, Subnet mask and DNS Server details. If I use same settings on other linux virtual box, it is able get that static ip address. The issue is only with Windows 2008 image.
    Here few more inputs that may help:
    - Windows 2008 image has "Bridge" adapter.
    - Host system is connected to corporate network via wired connection and NOT on VPN.
    - If I use "Obtain IP address automatically" setting, then it is able to get a dynamic IP address and internet is working fine.
    Questions:
    1. Has anyone seen this issue before ?
    2. Do I need to do any additional configuration on Windows 2008 server ?
    Thanks,
    GK

    Hi,
    Method 1: Uninstall and reinstall network drivers.
    Method 2: If you have any anti-virus software, disable them.
    You can also try set a static IP via neetsh commend.
     How to Use the NETSH Command to Change from Static IP Address to DHCP in Windows 2000
    http://support.microsoft.com/kb/257748
    Hope this helps.

  • System.Windows.Forms.SaveFileDialog not working under Windows 2008 R2 Server

    I am using Windows Server 2008 R2 (64-bit) that is been virtualized with Hyper-V and it is being used as a "Remote Desktop Server".
    I am trying to use this PowerShell code that will open a "Save-File-Dialog" box to select the PDF file and send it to my "batch" file for scanning.  This code works great on my Windows Vista machine and my Windows 7 32-bit machine
    but I cannot get it to work on the "Windows 2008 R2 Server (64-bit)".  It will not come up with any window at all and it will not produce any errors at all, so I can't exactly google for this issue.  I am using PowerShell 2.0 from 2009.
    Any ideas?  I tried it from an Admin account and a regular domain users and neither worked at all, no errors, no window, no nothing.
    *** Update ***
        I took Out-Null out and I received this...
      GAC    Version        Location
    True   v2.0.50727     C:\Windows\assembly\GAC_MSIL\System.Windows.Forms\2.0.0.0__b77a5c561934e089\System.Windows.Forms.dll
    I then checked the path and the DLL file was in there and it had read and execute permissions for Domain users and Administrators and the window still won't pop up... 
    Here is the entire code in question.....
    # Uses the dot net assembly to give the users a Save-File-Dialog box so they can decide where to put the pdf file
    Function Get-SaveFile($initialDirectory){
    [System.Reflection.Assembly]::LoadWithPartialName("System.windows.forms") | Out-Null
    $SaveFileDialog = New-Object System.Windows.Forms.SaveFileDialog
    $SaveFileDialog.initialDirectory = $initialDirectory
    $SaveFileDialog.filter = "PDF files (*.pdf)| *.pdf"
    $SaveFileDialog.ShowDialog() | Out-Null
    $SaveFileDialog.filename
    # open dialog box to select the .nessuss file.
    $OutputFile = Get-SaveFile
    # User selected where they want to put the scanned.pdf file and it will automatically set it to .pdf for them
    start-process Scan $OutputFile

    I ran the code you have in your function on a Windows 2008 Standard server, and it seems to be hanging on the line
    $SaveFileDialog.ShowDialog()
    | Out-Null
    It just sits there and nothing happens, but if I run it on my Windows 7 machines, it runs without any issues. So it seems like the dialog opened, but behind the scenes, and is waiting on the user, but since it doesn't open, the user can't do anything.
    If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful.
    Don't Retire Technet

  • Slow printing from windows 2008 R2 with Cisco 6509

    Dear All,
    I am having a wiered issue in my network. We have a windows 2008 R2 print server. Normal documents print's fine. If you print a image or pdf file, it takes a long time to print. For example a 2 MB PDF image with two page took me 10 minutes to print. The data from the server to the physical printer is really slow. To test it, i have loaded the driver on another windows 2008 R2 and the result is same slowness. We uses Xerox Colorqube 9303 printers.
    I have tried most options from microsoft which didnt help. I have installed a windows 2012 server to test if its specific to windows 2008, but the result remains same. Printing from a windows PC is perfectly fine; 32 bit PCs we have.
    I have seen someone got a solution to this by disabling ip local-proxy-arp, this is not enabled nor available in my switch.
    I have 6509 as core switch with IOS 12.2(33)SXH8. Does anybody come across such a scenario? Is there any special port configuration required for windows 2008 R2 to work normal?
    A sample interface configuration is given below
    GigabitEthernet1/10 is up, line protocol is up (connected)
      Hardware is C6k 1000Mb 802.3, address is c89c.1dd9.2619 (bia c89c.1dd9.2619)
      Description: ***Connect-to-Server-form***
      MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA, loopback not set
      Keepalive set (10 sec)
      Full-duplex, 1000Mb/s, media type is 10/100/1000BaseT
      input flow-control is off, output flow-control is on
      Clock mode is auto
      ARP type: ARPA, ARP Timeout 04:00:00
      Last input never, output 00:00:13, output hang never
      Last clearing of "show interface" counters never
      Input queue: 0/2000/88/0 (size/max/drops/flushes); Total output drops: 0
      Queueing strategy: fifo
      Output queue: 0/40 (size/max)
      5 minute input rate 0 bits/sec, 0 packets/sec
      5 minute output rate 151000 bits/sec, 30 packets/sec
         10067885 packets input, 4366947776 bytes, 0 no buffer
         Received 36631 broadcasts (2569 multicasts)
         0 runts, 0 giants, 0 throttles
         11 input errors, 1 CRC, 0 frame, 77 overrun, 0 ignored
         0 watchdog, 0 multicast, 0 pause input
         0 input packets with dribble condition detected
         251401032 packets output, 96130506019 bytes, 0 underruns
         0 output errors, 0 collisions, 5 interface resets
         0 babbles, 0 late collision, 0 deferred
         0 lost carrier, 0 no carrier, 0 PAUSE output
         0 output buffer failures, 0 output buffers swapped out
    Any help would be really appreciated.
    Thanking you in advance.
    Prince Mathew

    Hello
    Printing from a windows PC is perfectly fine; 32 bit PCs we have.
    - Printing directly from a computer which has the locally installed driver is printing fine.- it does seem to suggest the server or the network- however locally installed print drivers work fine so the communication to the printer from the client over the network seem to be okay.
    However the centrally installed print drivers means the processing job is now  with the server which is between the printer and client
    Whats the RTT from client and server and client to printer .etc?  - perform a extended ping to validate connectivity between all 3
    Have you hardcoded the server port to the nic setting of the server - Are the speed/duplex settings manually applied to the servers  if so make sure they are also manually set on the switch ports realting to these servers - this is apllicable to the printers too.
    Is the same driver used locally is also on the printer server correct?
    Whats printing protocol ( RAW) and port being used on the printer server
    Do you have print pooling setup on the server -(typo in last post)
    Are these printer shared in A/D and deployed by GPO -are the correct permissions set on these shares
    Check the printer permission on the spool folder also - users need at least read & execute privileges
    Have you manually cleared the print spooler folder and restarted the spooler service on the server?
    Are the print jobs being render to the clients or is the server taking the load of processing the print job?
    Any printer queue priorites set?
    res
    Paul
    Please don't forget to rate any posts that have been helpful.
    Thanks.

  • Windows 2008 R2 file copy freezing

    I have two windows 2008 R2 64  bit servers. I'm trying to copy a large amount of files (over 1000/as little as 500 mg) and at about 30-40% it just hangs. waited overnight a few times but no change. The nic is set to 1 gig full auto and verified that
    the port is as well. 
     Nic is a Broadcom BCM5709c NetXtreme IIGigE. 
    I have disabled IPV4 large send offload and IPV4 checksum offload. 
    IPV6 is disabled on the cards already.

    How you are copying these files ?  is it normal copy / paste or Robocopy ?
    For larger files, You have to user Robocopy as best practice, 
    Please go through below Robocopy library link and complete your task using Robocopy
    http://technet.microsoft.com/en-us/library/cc733145.aspx
    Regards,
    Manjunath Sullad

Maybe you are looking for