Windows 7 Enterprise and Windows 2008 R2 RDS

Hello folks,
Using SRSS 4.2 / SRWC 2.2 with Sun Ray Connector Windows Components software installed on the clients.
Our test show amazing screen speed, and full 32 bit colour depth, great flash speed on Windows 2008 R2 RDS but no audio.
Our test using Windows 7 Enterprise displayed fast graphic speed, Windows Aero disabled, no audio and cannot be changed thus the user experience is not pleasant.
Anyone know when this will be addressed as it is crucial for any new deployments and upcoming desktop refreshes.
Thanks!

After talking with Sun Support, this is a known bug that is slated to get fixed in the next SRWC patch. No timeline was available for the patch.
Edited by: segfaultcoredump on Jan 14, 2010 9:11 AM

Similar Messages

  • Windows 2008 R2 RDS Licensing Issue

    I have Citrix Presentation Server 4.5 farm (with all of the application servers running Windows 2003) and I have just migrated from using a Windows 2003 server for the terminal services licensing to a Windows 2008 R2 RDS server for the licensing. We have
    a number of thin-clients that connect to the Citrix farm and provide a kiosk for users. We have 85 per device licenses however we are only using 15 of those licenses (plans were made but never implemented to use the rest), so we have 70 available licenses.
    The licenses are configured per device and as Windows Server 2003 licenses.
    After the migration to 2008 R2, the thin-clients connected to the new licensing server without any trouble at all. As I monitored the licenses on the new server, each thin-client was given a temporary license first and then at the
    next connection they got a permanent license. All of this I have been able to confirm through the event logs on the server.
    However, what I get in the event logs of the new 2008 R2 licensing server an event with event ID 21 that says:
    The Remote Desktop license server "ServerName" does not have any remaining permanent Remote Desktop Services client access licenses (RDS CALs) of the type "Windows Server 2003 - TS Per Device CAL". As a result, the Remote Desktop license server cannot issue
    RDS CALs of the type "Windows Server 2003 - TS Per Device CAL" to the Remote Desktop Session Host server "vvv.xxx.yyy.zzz". To resolve this problem, verify that the Remote Desktop licensing mode configured on the RD Session Host server matches the type of
    RDS CALs installed on the Remote Desktop license server. If required, purchase and install additional RDS CALs as needed for this Remote Desktop license server.
    (Note I have removed the server name and IP address due to company policy.) I have confirmed that every server in my Citrix farm has its terminal services configuration set for "per device" licensing and I have also specified the name of the 2008
    R2 server rather than allow the servers to automatically find the licensing server. I have confirmed that my 2008 R2 server is configured for "per device" licensing.
    The IP addresses I have seen in the event log messages are the IP addresses of a Citrix server rather than one of the thin-clients, and so far every Citrix server we have has appeared in one of these event log messages. I have been able
    to determine that this event does not occur when a thin-client is connecting up nor does this event occur when I remotely log into the server.
    As I noted above we only have 15 thin-clients using the 85 licenses so we have 70 available licenses for the Citrix servers so why are we out of licenses? What is this message trying to tell me?
    Thanks
    Brent

    Hi Bent,
    According the Event ID 21, I think you might have the license connection issues with RDS CALs. I suggest you analyze some relative services and
    make sure your network without any misconfiguration.
    Hopefully, there is an article describes how to troubleshoot this license issue on the terminal server.
    Event ID 21 — Terminal Services Client Access License (TS CAL)
    http://technet.microsoft.com/en-US/library/A98D84AC-B824-4F00-BF58-3CFF23493BF9.aspx
    By the way, the license of Windows Server 2003 does not support to assign CAL to allow user to access the Windows Server 2008. You should buy a
    new Windows Server 2008 license to meet the requirement above if necessary.
    Hope this helps.

  • Question concerning the state of licenses of a Windows 2008 R2 RDS server after disolving the Domain, the DC, and the AD.

    Background: - several months back a Windows 2008 r2 domain existed with a DC, and an AD.  Windows servers where apart of this domain.  One of the servers being a Windows 2008 R2 server with Remote Desktop Services loaded.  The server was properly
    licensed for 8 User CALS.  All was operating correctly.  Since that time the domain has been removed, the DC removed and the AD removed.  What is left are Windows 2008 R2 servers in a workgroup.  Again, one being the Remote Desktop Server.
    Q1. Can the functioning Per User CALs (totaling 8) remain as Per User CALs?
    Q2. Am I required to switch them to 8 Per Device CALs?
    Referencing: "Best practices for setting up Remote Desktop Licensing...." - Article 2473823
    In the above article it states under "RDS HOST and RDS Licensing servers are in the same Workgroup" that "We can use ONLY Per Device CALs in a workgroup environment. So, you should install only Per Device CALs on RDS licensing server."
    ( Which in my case they are both the same server.
    Any information regarding what licensing options that can be used on a workgroup RDS server would be appreciated.

    Hi,
    Yes, agree with the supporting article which you have commented. We can only use per device CAL under workgroup environment and if you want to use per user CAL then server need to be member of domain. 
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support
    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]

  • Migrating roaming profile from Windows 2000 TS to Windows 2008 R2 RDS

    We have one TS running on Windows 2000. There are over 200 TS users. We are planning to migrate it to Windows 2008 R2. What's the easy way to migrate the roaming profile? Base on this article
    Support guidelines for migrating
    roaming user profiles data to ...
    Generally, user profiles that you create for users in Windows 2000, ... Server  2003 roaming user profile on Windows Vista or on Windows Server
    2008. ...  These methods migrate the
    roaming profile data to the new Version 2 user profile  format ...
    support.microsoft.com
    support.microsoft.com/kb/947025
    There are two methods to migrate roaming profile. "Method 2: Use the Folder Redirection feature to share data between Version 1 and Version 2 user profiles" doesn't "migrate the desktop settings and preferences such as wallpaper because of
    the differences in the operating systems". That isn't for us.
    "Method 1: Use the User State Migration Tool to migrate profile data to the new format (Windows Vista Only)" is recommend that you the User State Migration Tool (USMT) to migrate profile data in the following scenarios:
    You do not use roaming user profiles or folder redirection.
    You want to enable a more full-featured migration of user profile data from Windows 2000-based or from Windows XP-based systems to Windows Vista-based systems.
    Note The User State Migraton Tool will not function on Windows Server 2008. 
    So the method 1 doesn't work. Any suggestions?
    Bob Lin, MCSE & CNE Networking, Internet, Routing, VPN Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Install and Configure Windows, VMware, Virtualization and Cisco on http://www.HowToNetworking.com

    Hi,
    Thanks for your comment.
    Please check following article might helpful in your case.
    Hey, Scripting Guy! How Can I Edit Terminal Server Profiles for Users in Active Directory?
    http://blogs.technet.com/b/heyscriptingguy/archive/2008/10/23/how-can-i-edit-terminal-server-profiles-for-users-in-active-directory.aspx
    Configure Terminal Server User Profile – PowerShell Script
    https://gallery.technet.microsoft.com/scriptcenter/d36bd6b8-91b4-482b-8f67-9016cf367dbe
    How to assign a home folder to a user
    http://support.microsoft.com/kb/816313
    Sample script from above article.
    NET USER tester /add /comment:"Example Account for User"
    /expires:never
    /homedir:\\zippy\%username%$
    /profilepath:\\zippy\profile
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • Windows 2008 R2 RDS & HP P1505

    We run a Win 2008 R2 remote desktop server and are having some trouble with our P1505's. 
    - MS' EasyPrint feature works fine for small print jobs but on larger print jobs can balloon jobs into 30MB+ for 6 pages if there are graphics. 
    - There are no current drivers for Win2008R2 for the P1505 so bringing the printers into the session as network printers from the client's computer doesn't seem to work well either.  I've managed to install them using the Win2003x64 drivers but there is a weird quirk where each job sent to the printer shows up in the printer's que as two jobs, one of which prints and the other just sits there for 4-5 minutes, and nothing else will print until this job clears itself out.
    Any ideas when we can see proper drivers for this printer - or will they be released along side the Win7 drivers?
    Thanks

    i used the HP Laserjet 6L driver from windows update!!

  • GPP Delete policy not working on Windows Server 2008 R2 RDS when deleting shared printers with status access denied.

    Hi!
    I Have one AD Security group for each shared printer, I have one GPP that map the printer if the user is in the security group that belong to the printer. And one GPP to delete the printer if the user is NOT member of the security group. The security group
    is also applied in “Security” tab on the printsrv with PRINT rights  and “everyone” is removed. This works 100 % on Windows 7 clients and Windows 2003 Terminal Servers. But on Windows 2008 R2 RDS this dont work.The Delete Policy will not delete the shared
    printer. No warning in any logs, and the gpresult shows that the gpo setting applyed sucessfully. The only way I can make the Delete policy work is if i give the user print rights on the printer on the printsrv. Looks like for the policy to work on 2008
    R2 the user must have print rights on the printer object on the printserver. The GPP Delete Policy will not delete printers that have status : access denied. Anyone else had this problem?

    Hi,
    Based on your description, it seems that we need to give users appropriate permissions, for the error
    Access is denied is more or less related to permissions.
    However, we can avoid deploying the GPP printer delete policy. As far as I know, we can use Item-Lvel Targeting of GPP to push the shared printers
    to the targeted users or groups.
    Regarding ILT, the following articles can be referred to for more information.
    Preference Item-Level Targeting
    http://technet.microsoft.com/en-us/library/cc733022.aspx
    Security Group Targeting
    http://technet.microsoft.com/en-us/library/cc772471.aspx
    Best regards,
    Frank Shen

  • Windows 2008 Server Enterprise R2 x64 and Perc 4/dc SCSI driver issue

    Hello all, this is the first time posting so please forgive me if this has been posted here before.  I did try to search this issue but zero returns.
    OK, I have a Dell PowerEdge 2900.  I have just put a fresh install of MS Windows 2008 ENT. Server x64.  I cannot seem to find a driver for the PERC 4/dc SCSI controller I have installed.  I have been told the 2003 x64 driver would work so I attempted to install that driver but was unsuccessful.  Then I was told by Dell that the driver should be native to the OS.  Is the driver native to 2008 Server (or, supposed to be)?  Does anyone have an answer as to where I might retrieve am driver of the controller if not?  Anyway, thanks in advance

    Hello,
    I don't have a PowerEdge 2900, but I do have a PowerEdge 2850.  I'm also just a regular bloke like yourself that just happened upon your post and after I figured this driver debacle out I registered to hopefully help.
    The good thing is my PERC card is the same in the PE2850 as it is in your PE2900, as I'm utilizing a PERC 4/DC.  I've also managed to run into the same issue you ran into(?) trying to load Windows 2008 Server Enterprise R2 (support for 32bit processors have been removed in R2... so no more x86 versions... my poor PE2650s never stood a chance with this OS).   
    I can tell you officially from my experience/research Windows Server Enterprise R2 does not have support built into it for the PERC 4/DC card.
    However, I was able to download the Windows 2003 x64 driver from support.dell.com and make it work after much trial and error with newer releases of the PERC 4/DC driver that were not accepted by 2k8R2.
    Here's the link:  http://support.dell.com/support/downloads/download.aspx?c=us&cs=RC956904&l=en&s=hied&releaseid=R100373&SystemID=PWE_PNT_P3C_2850&servicetag=FBCLP61&os=WX64&osl=en&deviceid=6396&devlib=0&typecnt=0&vercnt=1&catid=-1&impid=-1&formatcnt=3&libid=35&fileid=129549
    File name (incase Dell moves it on you guys) is "perc-w2k3-6.46.3.64-A01.exe", date released 6/9/2005, build version 6.46.3.64, and the Dell revision number is A01. 
    Even though it states the driver is for the LSI Logic PERC 4e/Si it's sort of a mega pack including many other drivers such as the PERC 4/DC.  This was much relief because I was thinking I would need to stick with Windows 2008 until I found this driver for Windows 2008 R2.  :)
    What I did was:
    1) Downloaded the driver and extracted it to a USB drive.
    2) Booted-up via the Win2k8R2 CD and when it got to the screen where it asked to install to a partition and didn't show me a partition to install Win2k8R2 to I selected the option to load a driver. 
    3) From the load driver option I just browsed to the directory where I extracted the files and selected that directory.  If the "hide devices that are not compatible" option is selected (normally on by default) it will show you the proper driver. 
    4) Select the PERC 4/DC driver and then setup your partitions the way you would like them!  
    From there you should be able to boot into the OS... and really have some fun.
    Now you have the power... I guess the choice is yours to R2 or not to R2... that is the real question.  :)
    Enjoy!
    Dave
    Thanks and this worked for a Power edge 1800, PERC 4/DC as well. Kukan

  • Windows 2008 Licensing - Standard and Enterprise Edt - No of License required

    Hello All  , 
    We have a Windows Environment running on VMware (ESXi5.1), running Windows 2008 Standard and Enterprise platforms . We are working on the no of license that is required  for each category . Can you help us in licencing calculation for each environment
    .Below is the split 
    Windows 2008 R2 Standard Edt.
    ESX Cluster 1 
    Total No of ESX Hosts :4 
    Total No of Windows 2008 R2 Std Edt VMs : 9   // How many license req ? Calculation 
    Total No of Windows 2008 R2 Ent Edt VMs : 6    // How many license req ? Calculation 
    ESX Cluster 2 
    Total no of ESX Hosts : 3 
    Total No of Windows 2008 R2 Std Edt VMs : 13  // How many license req ? Calculation 
    Total No of Windows 2008 R2 Ent Edt VMs : 6   // How many license req ? Calculation 
    Appreciate your support 

    Hi Sathish,
    I would recommend you to contact the Microsoft Volume Licensing Service Center at the following
    Microsoft website. They are the experts and can guide you with the proper license requirments.
    https://www.microsoft.com/licensing/servicecenter/
    Find your local Volume Licensing Service Center support contact information below. Select your country from the drop-down list and the correct Support Center will
    be displayed at right.
    https://www.microsoft.com/licensing/servicecenter/Help/Contact.aspx
    Regards,
    Rafic
    If you found this post helpful, please give it a "Helpful" vote.
    If it answered your question, remember to mark it as an "Answer".
    This posting is provided "AS IS" with no warranties and confers no rights! Always test ANY suggestion in a test environment before implementing!

  • Windows 2008 Server and Windows 8 clients

    Hey Guys,
    I have had this problem for sometime now and really need a solution. I have Windows 2008 Enterprise Server running about 200+ terminal services clients. All Windows XP clients are fine, Windows 7 clients have issues when they get an updated version of
    remote desktop client(to solve the issue we simply rollback the update), Windows 8 clients cannot connect and use out remote app. The issue stems from the newer version of remote desktop client (on windows 7 and embedded in windows 8) cannot connect to our
    terminal server and generates an error and immediately disconnects. The error says "
    Your computer can't connect to the remote computer because an error occurred on the remote computer that you want
    to connect to
    So my questions are, how can i update my Windows 2008 Terminal server version to support these clients, or do u have migrate to Windows 2012? Or is there a solution to my current problem which will allow my client to connect and use the remoteapps?

    Hi,
    Thank you for posting in Windows Server Forum.
    Please follow the below steps and verify result.
    LAN manager authentication level settings (Local security policy->Local Policies->Security Options->Network Security: LAN Manager Authentication level). 
    Try to change it to "Send NTLMv2 response only" 
    Snap:
    If still face the issue please install this Hotfix.
    RDS client computer cannot connect to the RDS server by using a remote desktop connection in Windows
    http://support.microsoft.com/kb/2752618/
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • PKI SCCM Client Certificate Template not viewable by Windows 7 and Server 2008 workgroup machines.

    Hello everyone,
    I’m having issues with workgroup computers, not domain systems when I request a certificate.
    It’s extremely weird. It has something to do with Windows 7 and Windows 2008 machines. In 2003 server I can request a certificate manually with certutil and it see the certificate template. I copy over the exact command
    on windows 7 and it can’t see the certificate template.
    I have the following configuration:
    CA Enterprise
    I have created the SCCM Client Certificate
    I have created the SCCM Web Server Certificate
    I have created the SCCM Distribution Point Certificate
    GPO is configured
    SCCM 2012 R2 CU2 configured to do HTTP and HTTPS
    Installed SCCM Client Certificate
    Installed SCCM Web Server Certificate
    Installed Distribution Point Certificate
    Deployed to a domain computer good on PKI
    Workgroup Computers:
    I’m having issues with deploying certificates
    Windows 7 –
    (ERROR) not successful
    Windows Server 2008 R2 –
    (ERROR) not successful
    Windows Server 2003 - successful
    Windows XP – successful
    How I’m getting the certs for the clients is by utilizing the following scripts from this URL.
    http://www.ithierarchy.com/ITH/node/48
    I did find a couple of errors in the code, but if it’s working on my Server 2003, then it should work on the others. Windows 7 and Windows 2008 R2 seem to have the same issue. The error I’m getting is the following:
    Command line requesting the cert ---- CertReq –new –f testcomputer.home.pvt.inf c:\client\testcomputer.home.pvt.req
    Error --- Template not found.
    SCCMClientCertificate (this is my template)

    Just to give an update on what’s happening with this. I found out this format is unsupported by MS with Windows Vista and newer OS’s.
    Instead you must utilize two other additional roles on the CA to have this work. The caviate is, I’m down to the testing and it’s not working as in the document. I have MS Support
    working with me to resolve this issue since it was written by MSFT.
    http://blogs.technet.com/b/askds/archive/2010/05/25/enabling-cep-and-ces-for-enrolling-non-domain-joined-computers-for-certificates.aspx
    and use this doc for similar workgroup computers for rolling out certs. This was written for RT devices, however, it should work once I get to that point.
    http://blogs.technet.com/b/pki/archive/2012/12/11/certificate-for-winrt-devices-and-non-domain-member-devices.aspx

  • PKI Client Certificate Template not viewable by Windows 7 and Server 2008 workgroup machines.

    Hello everyone,
    I’m having issues with workgroup computers, not domain systems when I request a certificate.
    It’s extremely weird. It has something to do with Windows 7 and Windows 2008 machines. In 2003 server I can request a certificate manually with certutil and it see the certificate template. I copy over the exact command
    on windows 7 and it can’t see the certificate template.
    I have the following configuration:
    CA Enterprise
    I have created the SCCM Client Certificate
    I have created the SCCM Web Server Certificate
    I have created the SCCM Distribution Point Certificate
    GPO is configured
    SCCM 2012 R2 CU2 configured to do HTTP and HTTPS
    Installed SCCM Client Certificate
    Installed SCCM Web Server Certificate
    Installed Distribution Point Certificate
    Deployed to a domain computer good on PKI
    Workgroup Computers:
    I’m having issues with deploying certificates
    Windows 7 –
    (ERROR) not successful
    Windows Server 2008 R2 –
    (ERROR) not successful
    Windows Server 2003 - successful
    Windows XP – successful
    How I’m getting the certs for the clients is by utilizing the following scripts from this URL.
    http://www.ithierarchy.com/ITH/node/48
    I did find a couple of errors in the code, but if it’s working on my Server 2003, then it should work on the others. Windows 7 and Windows 2008 R2 seem to have the same issue. The error I’m getting is the following:
    Command line requesting the cert ---- CertReq –new –f testcomputer.home.pvt.inf c:\client\testcomputer.home.pvt.req
    Error --- Template not found.
    SCCMClientCertificate (this is my template)

    Just to give an update on what’s happening with this. I found out this format is unsupported by MS with Windows Vista and newer OS’s.
    Instead you must utilize two other additional roles on the CA to have this work. The caviate is, I’m down to the testing and it’s not working as in the document. I have MS
    Support working with me to resolve this issue since it was written by MSFT.
    http://blogs.technet.com/b/askds/archive/2010/05/25/enabling-cep-and-ces-for-enrolling-non-domain-joined-computers-for-certificates.aspx
    and use this doc for similar workgroup computers for rolling out certs. This was written for RT devices, however, it should work once I get to that point.
    http://blogs.technet.com/b/pki/archive/2012/12/11/certificate-for-winrt-devices-and-non-domain-member-devices.aspx

  • Remote desktop connection issue with an RDP client while connecting to some of windows 2008 and 2003 operating system flavors and not receiving SDin value choice 26 from DomainMCSPDU

    Hi Team
    We have our RDP client and i came across with one issue "Expected data got 3" with this client.
    This issue is getting while connecting some of below operating system flavors.
    Microsoft Windows 2008 Enterprise edition
    Microsoft Windows 2008 Standard edition
    Microsoft Windows 2003 servers
    When we are trying to get RDP to those servers with our client, getting "Expected data got 3" error. One more main thing here is the specified error is not getting for all the servers of same operating system in above list.
    Able to get the RDP console for those servers using mstsc client.
    When i read the [MS-RDPBCGR] specification, i found the below points
    mcsSDin (variable): Variable-length PER-encoded MCS Domain PDU (DomainMCSPDU) which encapsulates an MCS Send Data Indication structure (SDin, choice 26 from DomainMCSPDU), as specified in [T125] section 11.33 (the ASN.1 structure definitions
    are given in [T125] section 7, parts 7 and 10). The userData field of the MCS Send Data Indication contains a Security Header and a Valid Client License Data (section 2.2.1.12.1) structure.
    In my code i am not getting SDin value as 26. Is it the problem with Remote desktop Licensing in RDP servers as specified in the specification like "The userData field of the MCS Send Data Indication contains a Security Header and a Valid
    Client License Data (section 2.2.1.12.1) structure."
    Could you please explain me is this issue is happening due to Licence configuration in RDP server and please provide support with server side configuration if any because our code works for other servers ?
    Thanks & Regards,
    Pavan G.

    Hello Pavan -
    Thanks for contacting Microsoft Support. I'm researching this for you and request you to please send me mail at dochelp @ Microsoft dot com so that I can share tools and techniques to collect some traces and analyze.
    Thanks.
    Tarun Chopra | Escalation Engineer | Open Specifications Support Team

  • Windows 2008 Enterprise 32-bit Random Blue Screen 0x000000C4

    Hello,
    We have a customer with IBM x3500 M3 server, Windows 2008 Enterprise SP2 32-bit, 24GB RAM (Domain, file and print server, rdp server roles installed).
    Since December 2013, they have been experiencing random reboots (once or twice a month), so I ran debug on the memory.dmp and found that ntkrpamp.exe wa scausing this issue:
    Debug on memory.dmp file for January, 2014:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Debug\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available
    Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\Win2008E.DVD
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (12 procs) Free x86 compatible
    Product: LanManNt, suite: Enterprise TerminalServer
    Built by: 6002.18881.x86fre.vistasp2_gdr.130707-1535
    Machine Name:
    Kernel base = 0x82233000 PsLoadedModuleList = 0x8234ac70
    Debug session time: Wed Jan  8 08:24:19.852 2014 (UTC - 5:00)
    System Uptime: 4 days 0:37:56.528
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    *                        Bugcheck Analysis                                   
    Use !analyze -v to get detailed debugging information.
    BugCheck 50, {f85c5048, 0, 823af2bf, 0}
    Probably caused by : ntkrpamp.exe ( nt!CmpCheckKey+61b )
    Followup: MachineOwner
    9: kd> !analyze -v
    *                        Bugcheck Analysis                                   
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: f85c5048, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 823af2bf, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 00000000, (reserved)
    Debugging Details:
    READ_ADDRESS:  f85c5048
    FAULTING_IP:
    nt!CmpCheckKey+61b
    823af2bf 394724          cmp     dword ptr [edi+24h],eax
    MM_INTERNAL_CODE:  0
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    TRAP_FRAME:  97b7d9ec -- (.trap 0xffffffff97b7d9ec)
    ErrCode = 00000000
    eax=00000000 ebx=e6b30024 ecx=19ef8172 edx=00000035 esi=a559e6a8 edi=f85c5024
    eip=823af2bf esp=97b7da60 ebp=97b7da8c iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    nt!CmpCheckKey+0x61b:
    823af2bf 394724          cmp     dword ptr [edi+24h],eax ds:0023:f85c5048=????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from 82280de4 to 822cb292
    STACK_TEXT:  
    97b7d9d4 82280de4 00000000 f85c5048 00000000 nt!MmAccessFault+0x10b
    97b7d9d4 823af2bf 00000000 f85c5048 00000000 nt!KiTrap0E+0xdc
    97b7da8c 823b581a 01000001 009c4020 009c3f70 nt!CmpCheckKey+0x61b
    97b7dabc 823b5e48 a559e6a8 01000001 00000006 nt!CmpCheckRegistry2+0x8c
    97b7db04 823b086e 01000001 97b7dc60 8000a05c nt!CmCheckRegistry+0xf5
    97b7db60 823b2fdd 97b7dbb4 00000005 00000000 nt!CmpInitializeHive+0x4c1
    97b7dbd8 823b527d 97b7dc60 00000000 97b7dc4c nt!CmpInitHiveFromFile+0x19e
    97b7dc18 823ab4c5 97b7dc60 00000000 97b7dc7b nt!CmpCmdHiveOpen+0x36
    97b7dd14 823ab6fa 00000002 8232b5a0 00000002 nt!CmpFlushBackupHive+0x2fd
    97b7dd38 8248acbd 8233513c 8e9462d8 822d8d4a nt!CmpSyncBackupHives+0x90
    97b7dd44 822d8d4a 00000000 00000000 8e9462d8 nt!CmpPeriodicBackupFlushWorker+0x32
    97b7dd7c 8240901c 00000000 8e585cb2 00000000 nt!ExpWorkerThread+0xfd
    97b7ddc0 82271eee 822d8c4d 00000001 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
    STACK_COMMAND:  kb
    FOLLOWUP_IP:
    nt!CmpCheckKey+61b
    823af2bf 394724          cmp     dword ptr [edi+24h],eax
    SYMBOL_STACK_INDEX:  2
    SYMBOL_NAME:  nt!CmpCheckKey+61b
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrpamp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  51da1840
    FAILURE_BUCKET_ID:  0x50_nt!CmpCheckKey+61b
    BUCKET_ID:  0x50_nt!CmpCheckKey+61b
    Followup: MachineOwner
    Based on google searches, driver verifier was recommended to be turned on to track driver with fault. I enabled verifier on all drivers, disabled automatic server reboot and today server crashed again.
    here's the debug output of full memory.dmp file:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\windows\memory.dmp]
    Kernel Summary Dump File: Only kernel address space is available
    Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\Win2008E.DVD
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (12 procs) Free x86 compatible
    Product: LanManNt, suite: Enterprise TerminalServer
    Built by: 6002.18881.x86fre.vistasp2_gdr.130707-1535
    Machine Name:
    Kernel base = 0x82214000 PsLoadedModuleList = 0x8232bc70
    Debug session time: Thu Feb 13 08:29:07.272 2014 (UTC - 5:00)
    System Uptime: 3 days 23:15:45.259
    Loading Kernel Symbols
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 7ffdd00c).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    *                        Bugcheck Analysis                                   
    Use !analyze -v to get detailed debugging information.
    BugCheck C4, {e2, af033d18, 2d0000, 0}
    Page 6684ef not present in the dump file. Type ".hh dbgerr004" for details
    Page 66a0f9 not present in the dump file. Type ".hh dbgerr004" for details
    Probably caused by : srvnet.sys ( srvnet!SrvNetWskSendData+c9 )
    Followup: MachineOwner
    9: kd> !analyze -v
    *                        Bugcheck Analysis                                   
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 000000e2, IRP field is a user-mode address but Irp->RequestorMode is KernelMode.
    Arg2: af033d18, IRP address.
    Arg3: 002d0000, User-mode address present as the value of an IRP field.
    Arg4: 00000000
    Debugging Details:
    Page 6684ef not present in the dump file. Type ".hh dbgerr004" for details
    Page 66a0f9 not present in the dump file. Type ".hh dbgerr004" for details
    BUGCHECK_STR:  0xc4_e2
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  spoolsv.exe
    CURRENT_IRQL:  2
    LAST_CONTROL_TRANSFER:  from 824ff5a7 to 822e19bd
    STACK_TEXT:  
    eff67a20 824ff5a7 000000c4 000000e2 af033d18 nt!KeBugCheckEx+0x1e
    eff67a40 824fea32 af033d18 002d0000 9930e2e0 nt!VerifierBugCheckIfAppropriate+0x32
    eff67a58 824fe7e0 af033d18 9930e2e0 99269b80 nt!ViIrpCheckKernelAddressForIrp+0x51
    eff67a70 824f766d 99269b80 af033458 99269b80 nt!VfBeforeCallDriver+0x3d
    eff67a90 82258931 af033fa4 af033fe0 99269b80 nt!IovCallDriver+0x1ef
    eff67aa4 9b01271a eff67adc aad3183f bd99d34c nt!IofCallDriver+0x1b
    eff67aac aad3183f bd99d34c eff67ad0 00000002 afd!WskProAPISend+0x67
    eff67adc aad31490 9b01d9d0 af033d18 af033458 srvnet!SrvNetWskSendData+0xc9
    eff67afc aad779d2 d5b93018 af033458 00000030 srvnet!SrvNetSendData+0x4d
    eff67b14 aadb45bd af033368 aad75459 af033d18 srv!SrvStartSend2+0xa3
    eff67b40 aad7522d af033fa4 eff67b84 824f7d4d srv!SrvFsdRestartReadAndX+0x127
    eff67b4c 824f7d4d 00000000 af033d18 af033368 srv!SrvFsdIoCompletionRoutine+0x1d
    eff67b84 822bb0fb 00000000 af033d18 eff67bf0 nt!IovpLocalCompletionRoutine+0x16e
    eff67bb8 824f7b95 824f7a77 ccb4e7c8 eff67c44 nt!IopfCompleteRequest+0x11d
    eff67c28 981a30d9 c3fbc2d8 ccb4e7c8 909c9dd0 nt!IovCompleteRequest+0x11c
    eff67c4c 824f76be 909c9dd0 ccb4e7c8 9efe80e8 Npfs!NpFsdWrite+0x53
    eff67c70 82258931 ccb4e838 ccb4e7c8 909c9dd0 nt!IovCallDriver+0x23f
    eff67c84 8245ae25 9efe8114 ccb4e7c8 ccb4e838 nt!IofCallDriver+0x1b
    eff67ca4 82427b13 909c9dd0 9efe80e8 00000001 nt!IopSynchronousServiceTail+0x1d9
    eff67d38 8225ec96 909c9dd0 00000a39 00000000 nt!NtWriteFile+0x6fc
    eff67d38 77755d14 909c9dd0 00000a39 00000000 nt!KiSystemServicePostCall
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0549f880 00000000 00000000 00000000 00000000 0x77755d14
    STACK_COMMAND:  kb
    FOLLOWUP_IP:
    srvnet!SrvNetWskSendData+c9
    aad3183f 53              push    ebx
    SYMBOL_STACK_INDEX:  7
    SYMBOL_NAME:  srvnet!SrvNetWskSendData+c9
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: srvnet
    IMAGE_NAME:  srvnet.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4dbabc34
    FAILURE_BUCKET_ID:  0xc4_e2_VRF_srvnet!SrvNetWskSendData+c9
    BUCKET_ID:  0xc4_e2_VRF_srvnet!SrvNetWskSendData+c9
    Followup: MachineOwner
    Here's the output of mini dump file as well:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\windows\minidump\Mini021314-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\Win2008E.DVD
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (12 procs) Free x86 compatible
    Product: LanManNt, suite: Enterprise TerminalServer
    Built by: 6002.18881.x86fre.vistasp2_gdr.130707-1535
    Machine Name:
    Kernel base = 0x82214000 PsLoadedModuleList = 0x8232bc70
    Debug session time: Thu Feb 13 08:29:07.272 2014 (UTC - 5:00)
    System Uptime: 3 days 23:15:45.259
    Loading Kernel Symbols
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    Loading User Symbols
    Loading unloaded module list
    *                        Bugcheck Analysis                                   
    Use !analyze -v to get detailed debugging information.
    BugCheck C4, {e2, af033d18, 2d0000, 0}
    Probably caused by : srvnet.sys ( srvnet!SrvNetWskSendData+c9 )
    Followup: MachineOwner
    9: kd> !analyze -v
    *                        Bugcheck Analysis                                   
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 000000e2, IRP field is a user-mode address but Irp->RequestorMode is KernelMode.
    Arg2: af033d18, IRP address.
    Arg3: 002d0000, User-mode address present as the value of an IRP field.
    Arg4: 00000000
    Debugging Details:
    BUGCHECK_STR:  0xc4_e2
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  spoolsv.exe
    CURRENT_IRQL:  2
    LAST_CONTROL_TRANSFER:  from 824ff5a7 to 822e19bd
    STACK_TEXT:  
    eff67a20 824ff5a7 000000c4 000000e2 af033d18 nt!KeBugCheckEx+0x1e
    eff67a40 824fea32 af033d18 002d0000 9930e2e0 nt!VerifierBugCheckIfAppropriate+0x32
    eff67a58 824fe7e0 af033d18 9930e2e0 99269b80 nt!ViIrpCheckKernelAddressForIrp+0x51
    eff67a70 824f766d 99269b80 af033458 99269b80 nt!VfBeforeCallDriver+0x3d
    eff67a90 82258931 af033fa4 af033fe0 99269b80 nt!IovCallDriver+0x1ef
    eff67aa4 9b01271a eff67adc aad3183f bd99d34c nt!IofCallDriver+0x1b
    eff67aac aad3183f bd99d34c eff67ad0 00000002 afd!WskProAPISend+0x67
    eff67adc aad31490 9b01d9d0 af033d18 af033458 srvnet!SrvNetWskSendData+0xc9
    eff67afc aad779d2 d5b93018 af033458 00000030 srvnet!SrvNetSendData+0x4d
    eff67b14 aadb45bd af033368 aad75459 af033d18 srv!SrvStartSend2+0xa3
    eff67b40 aad7522d af033fa4 eff67b84 824f7d4d srv!SrvFsdRestartReadAndX+0x127
    eff67b4c 824f7d4d 00000000 af033d18 af033368 srv!SrvFsdIoCompletionRoutine+0x1d
    eff67b84 822bb0fb 00000000 af033d18 eff67bf0 nt!IovpLocalCompletionRoutine+0x16e
    eff67bb8 824f7b95 824f7a77 ccb4e7c8 eff67c44 nt!IopfCompleteRequest+0x11d
    eff67c28 981a30d9 c3fbc2d8 ccb4e7c8 909c9dd0 nt!IovCompleteRequest+0x11c
    eff67c4c 824f76be 909c9dd0 ccb4e7c8 9efe80e8 Npfs!NpFsdWrite+0x53
    eff67c70 82258931 ccb4e838 ccb4e7c8 909c9dd0 nt!IovCallDriver+0x23f
    eff67c84 8245ae25 9efe8114 ccb4e7c8 ccb4e838 nt!IofCallDriver+0x1b
    eff67ca4 82427b13 909c9dd0 9efe80e8 00000001 nt!IopSynchronousServiceTail+0x1d9
    eff67d38 8225ec96 909c9dd0 00000a39 00000000 nt!NtWriteFile+0x6fc
    eff67d38 77755d14 909c9dd0 00000a39 00000000 nt!KiSystemServicePostCall
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0549f880 00000000 00000000 00000000 00000000 0x77755d14
    STACK_COMMAND:  kb
    FOLLOWUP_IP:
    srvnet!SrvNetWskSendData+c9
    aad3183f 53              push    ebx
    SYMBOL_STACK_INDEX:  7
    SYMBOL_NAME:  srvnet!SrvNetWskSendData+c9
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: srvnet
    IMAGE_NAME:  srvnet.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4dbabc34
    FAILURE_BUCKET_ID:  0xc4_e2_VRF_srvnet!SrvNetWskSendData+c9
    BUCKET_ID:  0xc4_e2_VRF_srvnet!SrvNetWskSendData+c9
    Followup: MachineOwner
    I'd like to know how to fix this. Server has up-to-date firmware and drivers from IBM. It's also up-to-date on all windows updates.
    Any help is greatly appreciated.
    Will

    This one may help.
    http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023(v=vs.85).aspx
    I'd test the RAM and or get with IBM on best method to verify the hardware and drivers.
    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.

  • CoCreateInstance returns 0x8007007e (Module could not be found) for the first call only at system startup on Windows 2008 Enterprise SP2

    Hi Guys,
    I'm experiencing a problem with CoCreateInstance, where it returns error 0x8007007e.
    The code is something like this:
    HRESULT hRes = S_OK;
    CComPtr<IMyInterface> spObj;
    if(FAILED(CoInitialize(NULL))) { /* quit */ }while(FAILED(hRes = spObj.CoCreateInstance(CLDIS_MyClass, NULL, CLSCTX_LOCAL_SERVER)))
    // LogFailure(hRes);
    Sleep(10);
    The problems occurs only on a single machine having Windows 2008 Enterprise SP2 installed (it works fine on other machines / OS versions). It happens only during the system startup (this is a Windows Service) and only for the first call of the CoCreateInstance.
    The second call always succeeds.
    The problem does not occurr when starting the service manually from Services.
    I did some investigation using Process Monitor and found that the HKCR\CLSID\[CLSID of MyClass]\LocalServer32!LocalServer32 registry value is accessed before the failure. The registry value exists - it is added by the Windows Installer during
    installation.
    If I remove the registry value then the CoCreateInstance always succeeds.
    I've been trying to lookup for some documentation on HKCR\CLSID\...\LocalServer32!LocalServer32 but haven't found anything useful other than it's a "Windows Installer Entrypoint". I assume that the Windows Installer does some integrity checks when
    calling CoCreateInstance for such class and this fails for some reason but currently I fail to find the reason.
    Can anyone help finding out what's the root cause of the 0x8007007e error here, please? Any help or tip is much appreciated.
    Many thanks!
    Marcin.

    Hi Marcin,
    This forum is mainly for talk about the product use related issue and not the best place to talk about the develop issue, for the develop issue we can post in MSDN forum for
    the further help and your issue may need capture a dump then for the further analysis it is not an efficient way to work in this community since we may need more resources which is not appropriate to handle in the community. I‘d like to suggest that you submit
    a service request to MS Professional tech support service so that a dedicated Support Professional can further assist with this request.
    MSDN forum
    https://social.msdn.microsoft.com/Forums/en-US/home
    Please visit the below link to see the various paid support options that are available to better meet your needs.
    http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone
    Thanks for your understanding and support.
    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]

  • Getting Group Policies to work on Windows 8.1 Enterprise and Windows 2012R2

    Just have a question about applying GPO's to Windows 8.1 Enterprise PC's. We have Windows server 2008 R2 DC's in our environment, so if we want to use the new policy definitions for Windows 8.1 Enterprise, we have to download them and put them in the Central
    store on the Windows 2008 R2 DC server, will this be enough ? Or we have to Extend the schema of our Active directory to Windows 2012 R2 first by adding 2012 R2 DC to our Active Directory.
    In otherwords what are the requirements for appying the new Windows 8.1 policy definitions in our Windows 2008 R2 environment ?

    > have to download them and put them in the Central store on the Windows
    > 2008 R2 DC server, will this be enough ?
    For ADM templates: Yes.
    > Or we have to Extend the schema
    For "some" settings, yes. Bitlocker Key storage, eg.
    > In otherwords what are the requirements for appying the new Windows 8.1
    > policy definitions in our Windows 2008 R2 environment ?
    Define "policy definitions" :)
    Martin
    Mal ein
    GUTES Buch über GPOs lesen?
    NO THEY ARE NOT EVIL, if you know what you are doing:
    Good or bad GPOs?
    And if IT bothers me - coke bottle design refreshment :))

Maybe you are looking for