Windows 2008 Group Policy not working in Windows 8.1

Hi ,
We found that the GPO settings created in Windows 2008 is not working in a Windows 8.1 machine.
One example is the proxy settings.
We confirmed from gpresult that the GPO is in the list but checking the actual proxy settings, it is not applied.
Regards,
Jhun

Hi,
How did we configure the proxy settings, using Internet Explorer Maintenance? If it is this case, just as Martin suggested, we can’t use IEM to manage
IE 10 and IE 11. However, we can configure the proxy setting via Group Policy Preferences (GPP).
Regarding this point, the following blog can be referred to for more information.
Configuring Internet Explorer 10′s
Proxy Via Group Policy
http://johnfail.wordpress.com/2013/06/15/configuring-internet-explorer-10s-proxy-via-group-policy/
In addition, when we use this GPP extension, pay attention to GPP F5-F8 keys.
Regarding this point, the following blog can be referred to for more information.
Group Policy Preferences F5 F6 F7 F8 “documentation”
http://msitpros.com/?p=1014
Please Note: Since the above two websites are not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy
of this information.
In addition, regarding the deprecation of IEM, the following article can be referred to for more information.
Appendix B: Replacements for Internet Explorer Maintenance
http://technet.microsoft.com/en-us/library/jj890998.aspx
Best regards,
Frank Shen

Similar Messages

Windows 2008 R2 does not work on Sunfire X4170

Hi, I recently bought a used X4170 server and have a weird problem. Windows 2008 R2 does not work, but 2012 does. I tried RTM version and a version with SP1. The problem is this:
After installing, I set the password and windows just displays a blank desktop, sometimes it boots but freezes soon after - the mouse cursor moved but nothing else works.
Booting in Safe Mode works and Windows do not freeze. The Event Log contains lots and lots (about 20 per second) of these entries:
Log Name:
System
Source:
Microsoft-Windows-WHEA-Logger
Date:
6/21/2014 12:24:59 AM
Event ID:
17
Task Category: None
Level:
Warning
Keywords:
User:
LOCAL SERVICE
Computer:
WIN-SOGS2TPM334
Description:
A corrected hardware error has occurred.
Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)
Bus:Device:Function: 0x0:0x0:0x0
Vendor ID:Device ID: 0x8086:0x3406
Class Code: 0x30000
I have tried updating the driver for this device (downloaded from Intel), no difference. Is there a way to make Windows 2008 R2 work on this server?

Hello
Thank you for the update.
Please refer the below Knowledge document related to this issue:
Windows BSOD WHEA_UNCORRECTABLE_ERROR(124) & correctable WHEA events when disabling network ports on X4170M2/X4270M2 (Doc ID 1576683.1)
However above document talks about X4170M2, I would suggest you to follow and if issue persist, please open Service Request with Oracle to diagnose further.
Best Regards
Bhavyesh

Windows 2008 R2 group policy not applied to windows 8 Workstations, but applied to XP and Win 7

I have a Windows 2008 R2 Domain Controllers and have a Policy to put a specify wallpaper, eventuality i have to change the Wallpaper, this setting applied sucesfully in Windows xp and Windows 7 workstations, but not applied in Windows 8 workstations even
if i run gpupdate /forcé,
Best Regards,
Thank you

Hi,
Thanks for posting in the forum.
Before going further, would you please let me know how did you configure the Group Policy setting to deploy the wallpaper? Have you configured some settings to limit the scope the GPO applying?
If all Windows 8 machines failed to receive the GPO settings? In order to narrow down the cause of the issue, I suggest we could try to collect the following information for troubleshooting.
GPMC.log
==================
a. On domain controller, click Start ->Run, type GPMC.MSC, it will load the GPMC console.
b. Right click on "Group Policy Result" and choose wizard to generate a report for the problematic computer and user account (please place appropriately). (Choose computer and select the proper
user in the wizard)
c. Right click
the resulting group policy result and click the "Save Report…" => save report to save the report to a HTML file.
Once we get the report, please check if the settings have been applied to the target correctly.
In addition, would you please let me know whether you have imported the latest Windows 8 Administrative Templates to the Windows Server 2008 DC? If not, please try to download and import it.
Then try to configure the wallpaper GPO settings again to see if it could help.
For details, please refer to the following articles.
Administrative Templates (.admx) for Windows 8 and Windows Server 2012
http://www.microsoft.com/en-us/download/details.aspx?id=36991
Set Desktop Background via Group Policy in Windows 7, Windows 8 in a Server 2008 or Server 2012 Domain
http://dizzyit.com/2013/04/14/set-desktop-background-group-policy-windows-7-windows-8-server-2008-server-2012-domain/
Hope this helps.
Best Regards,
Andy Qi
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Andy Qi
TechNet Community Support

Windows 2012 Group Policy Option missing for Windows 7 Client

Hi there,
We have a deployment with a windows 2012 DC and various Windows 7 clients.
I am trying to set up a group policy on the 2012 DC to configure the Windows 7 clients and basically disable the Aero feature.
The "Do not allow desktop composition" is the one I need to enable and this would sit under Admin Templates > Windows Components > Desktop Windows Manager.
In Windows 2012 Group Policy editor this does not show...does anyone know how I can do this to a remote Windows 7 machine from 2012 DC?
Note if it helps on a windows 7 machine you can also disable the service "Desktop Window Manager Session Manager”
to achieve the same thing BUT when looking through the Group Policy again I can’t seem to find this!!
Thanks for any help,
Steve

> In Windows 2012 Group Policy editor this does not show...does anyone
> know how i can do this to a remote Windows 7 machine from 2012 DC?
Install RSAT and edit on W7. Or copy all W7 admx/adml templates to the
central store.
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 :))

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- Account Lock not working and getting Domain Policy access denied

Hi
Windows 2008 Root Domain we tried to Edit the policy and we were getting the error "Access Denied on the Domain Policy template" we resolved by giving Write permission for authenticated user on the Template. later we applied account lock out policy.
but it is not applying and automatically reset to 0 in account lockout tool.
Error:"Access Denied:\\sysvol\Domain.com\policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Windows NT\SecEdit\GPTmpl.inf.Make sure that you have the right permission to this object.

Hi,
The error message is Access Denied, so it should be a permission issue.
You mentioned that you tested the account lockout in isolated network, it was working fine without any problem, by which did you mean that you didn’t get the Access Denied error message, or account wasn’t lockout out?
If you are facing account lockout problem, here are some troubleshooting articles below for you:
Troubleshooting Account Lockout
http://technet.microsoft.com/en-us/library/cc773155(v=WS.10).aspx
Troubleshooting account lockout the PSS way
http://blogs.technet.com/b/instan/archive/2009/09/01/troubleshooting-account-lockout-the-pss-way.aspx
Appendix Two: Gathering Information to Troubleshoot Account Lockout Issues
http://technet.microsoft.com/en-us/library/cc778156(v=WS.10).aspx
Best Regards,
Amy

New Group Policy not working on 2008 RDS in 2012 Domain - Security Filtering problem?

We have a Windows 2008 R2 RDS in a Windows 2012R2 Domain. We want to lockdown the 2008 RDS for Domain users that we have added to a new security Group--named "Data Collection Users". These users are "Domain Users" and login to the
2008 RDS using Windows XP SP3 machines to run a specific application -they do not use their local desktops for anything. WE added this group to the local RDU group on the RDS. We do not have any other users that login to the RDS through terminal,
including any Domain Admins.
So far we have done these steps:
On the DC, created new OU (called Terminal Servers) and moved the RDS into it.
Opened Group Policy on the DC, and under GP Objects, created a new policy called "TS Users Lockdown".
Linked the Policy to the OU.
Under Security Filtering we removed the Authenticated Users, added the RDS computer account (called QS2), added the "Data Collection Users" and chose Allow for "Read" and "Apply Policy"
Under Security Filtering, for Domain Admins, we chose Deny for "Apply Group Policy"
We edited the Policy (under Computer Configuration>AT>SYS>GP) to Enable Loopback processing - Replace mode.
We first tested the policy by trying to remove the "Run" from startup menu and "prohibit access to Control Panel".
We ran the Group Policy force update from within GP Management - ran successfully.
We did not reboot the RDS.
Neither of the settings we tried in Step 7 worked. Why Not?
Here are images from the Security Filtering:

Ok--Do I reboot the RDS or the DC? or both?
Does it look like my Security Filtering is correct? I have seen posts where you should not remove the "Authenticated users"?

Problem Windows 8 logon script not working from windows server 2008 R2

hi there , this is third post regard this problem, here is my problem goes .....
Is a very simple logon script for mapping drive purpose .... PLS take note Domain users can access and run this script for domain users using windows XP / WINDOWS VISTA / WINDOSWS 7 and only users " WINDOWS 8.1 " Does NOT run
at all . the script I put on logon script in Windows server 2008R2 group policy ...
@jrv :- http://social.technet.microsoft.com/profile/jrv/?ws=usercard-mini , insist said is my group policy setup problem so I post here agn...
Manually run the script on WINDOWS 8.1 is 100 % perfect so it is definitely not my logon script issue , PLS any guidance pls share for me ok ?? thanks
Below is my script syntax ;-
@echo off
REM Login.bat Version 1.0
REM Exit if user has logged on to the Server
IF %COMPUTERNAME%.==SL2011. GOTO END
REM Delete pre-existing drive mappings
REM
REM Map M: to SL2011 on sl2011
NET USE M: /DELETE >nul
NET USE M: \\SL2011\sl2011 /YES >nul
REM
REM Map Y: to AccScan on rss2
NET USE Y: /DELETE >nul
NET USE Y: \\rss2\Public\AccScan /YES >nul
REM

Hi Tee Ee Foong,
According to your post, the gpresult showed the GPO was applied and the script could run successfullymanully in the client. Right? Please follow the following step to narrow down
the issue:
1. Change the script to the following command: add
> %SystemDrive%\Users\test.txt to the script.
2. Log on to a client with a regular user account, run gpupdate/force, and then re-log on to this client.
3. Check if the test.txtfile exists in this location %SystemDrive%\Users.
If the test.txtfile exists, the GPO with logon script is applied successfully when user logs on. But the result of running logon script achieves the goal we excepted or not which
is still not sure.
Regards,
Lany Zhang

Disable the Server Manager popup in Unattended.xml for Windows 2008 R2 is not working

I have made entry into Unattended file to stop the popup of Server Manager during first starup of windows 2008 R2. However it is not working out, but Disable Initial OCnfiguration task window is working fine. Below is my Unattended.xml
file:
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" language="neutral" name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35"
versionScope="nonSxS">
<ImageInstall>
<OSImage>
<WillShowUI>OnError</WillShowUI>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>1</PartitionID>
</InstallTo>
<InstallFrom>
<Path>K:\win28x64\Sources\install.wim</Path>
<MetaData>
<Key>/image/name</Key>
<Value>Windows Server 2008 R2 SERVERENTERPRISE</Value>
</MetaData>
</InstallFrom>
</OSImage>
</ImageInstall>
<UpgradeData>
<Upgrade>false</Upgrade>
</UpgradeData>
<Display>
<ColorDepth>16</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<ComplianceCheck>
<DisplayReport>OnError</DisplayReport>
</ComplianceCheck>
<UserData>
<AcceptEula>true</AcceptEula>
</UserData>
</component>
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" language="neutral" name="Microsoft-Windows-International-Core-WinPE"
processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS">
<SetupUILanguage>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
<InputLocale>0409:00000409</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
</settings>
<settings pass="specialize"><component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" language="neutral" name="Microsoft-Windows-ServerManager-SvrMgrNc"
processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS">
<DoNotOpenServerManagerAtLogon>true</DoNotOpenServerManagerAtLogon>
</component><component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" language="neutral" name="Microsoft-Windows-OutOfBoxExperience" processorArchitecture="amd64"
publicKeyToken="31bf3856ad364e35" versionScope="nonSxS">
<DoNotOpenInitialConfigurationTasksAtLogon>true</DoNotOpenInitialConfigurationTasksAtLogon>
</component>
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" language="neutral" name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35"
versionScope="nonSxS">
<ComputerName>Siddu</ComputerName>
<RegisteredOrganization/>
<RegisteredOwner>BL-Target</RegisteredOwner>
<DoNotCleanTaskBar>true</DoNotCleanTaskBar>
<ShowWindowsLive>false</ShowWindowsLive>
<BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled>
<CopyProfile>false</CopyProfile>
<DisableAutoDaylightTimeSet>true</DisableAutoDaylightTimeSet>
<StartPanelOff>false</StartPanelOff>
</component>
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" language="neutral" name="Microsoft-Windows-UnattendedJoin"
processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS">
<Identification>
<JoinWorkgroup>Siddu</JoinWorkgroup>
<UnsecureJoin>false</UnsecureJoin>
<DebugJoin>false</DebugJoin>
</Identification>
</component>
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" language="neutral" name="Networking-MPSSVC-Svc" processorArchitecture="amd64"
publicKeyToken="31bf3856ad364e35" versionScope="nonSxS">
<FirewallGroups/>
<DomainProfile_EnableFirewall>false</DomainProfile_EnableFirewall>
<PrivateProfile_EnableFirewall>false</PrivateProfile_EnableFirewall>
<PublicProfile_EnableFirewall>false</PublicProfile_EnableFirewall>
<PrivateProfile_DisableNotifications>true</PrivateProfile_DisableNotifications>
</component>
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" language="neutral" name="Microsoft-Windows-TCPIP" processorArchitecture="amd64"
publicKeyToken="31bf3856ad364e35" versionScope="nonSxS">
<Interfaces>
<Interface wcm:action="add">
<Ipv4Settings>
<DhcpEnabled>false</DhcpEnabled>
</Ipv4Settings>
<Ipv6Settings>
<DhcpEnabled>true</DhcpEnabled>
</Ipv6Settings>
<UnicastIpAddresses>
<IpAddress wcm:action="add" wcm:keyValue="1">192.168.79.171/24</IpAddress>
</UnicastIpAddresses>
<Identifier>PROV_DEVICE_MAC_ADD</Identifier>
<Routes>
<Route wcm:action="add">
<Identifier>0</Identifier>
<Prefix>0.0.0.0/0</Prefix>
<NextHopAddress>192.168.79.0</NextHopAddress>
<Metric>20</Metric>
</Route>
</Routes>
</Interface>
</Interfaces>
</component>
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" language="neutral" name="Microsoft-Windows-DNS-Client" processorArchitecture="amd64"
publicKeyToken="31bf3856ad364e35" versionScope="nonSxS">
<Interfaces>
<Interface wcm:action="add">
<DNSServerSearchOrder>
<IpAddress wcm:action="add" wcm:keyValue="1">192.168.79.168</IpAddress>
</DNSServerSearchOrder>
<EnableAdapterDomainNameRegistration>true</EnableAdapterDomainNameRegistration>
<Identifier>PROV_DEVICE_MAC_ADD</Identifier>
</Interface>
</Interfaces>
</component>
</settings>
<settings pass="oobeSystem">
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" language="neutral" name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35"
versionScope="nonSxS">
<UserAccounts>
<AdministratorPassword>
<Value>PROV_WIN_ADMIN_PASSWORD</Value>
<PlainText>true</PlainText>
</AdministratorPassword>
</UserAccounts>
<AutoLogon>
<Enabled>true</Enabled>
<Username>Administrator</Username>
<Password>
<Value>PROV_WIN_ADMIN_PASSWORD</Value>
<PlainText>true</PlainText>
</Password>
<LogonCount>3</LogonCount>
</AutoLogon>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<CommandLine>c:\BLProv\wrapper.bat</CommandLine>
<Description>Lite Touch new OS</Description>
<Order>1</Order>
</SynchronousCommand>
</FirstLogonCommands>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Other</NetworkLocation>
<ProtectYourPC>3</ProtectYourPC>
<SkipUserOOBE>true</SkipUserOOBE>
<SkipMachineOOBE>true</SkipMachineOOBE>
</OOBE>
<RegisteredOrganization/>
<RegisteredOwner>BL-Target</RegisteredOwner>
<TimeZone>Dateline Standard Time</TimeZone>
</component>
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" language="neutral" name="Microsoft-Windows-International-Core"
processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS">
<InputLocale>0409:00000409</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
</settings>
<settings pass="offlineServicing">
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" language="neutral" name="Microsoft-Windows-PnpCustomizationsNonWinPE"
processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS">
<DriverPaths>
<PathAndCredentials wcm:action="add" wcm:keyValue="1">
<Path>C:\Drivers</Path>
</PathAndCredentials>
<PathAndCredentials wcm:action="add" wcm:keyValue="2">
<Path>X:\Drivers</Path>
</PathAndCredentials>
</DriverPaths>
</component>
</settings>
<cpi:offlineImage xmlns:cpi="urn:schemas-microsoft-com:cpi" cpi:source="wim:K:\win28x64\sources\install.wim#Windows Server 2008 R2 SERVERENTERPRISE"/>
</unattend>

Hi,
Since this issue is more related with Windows Server, I have helped you move this thread to that forum so that you could get help better.
Karen Hu
TechNet Community Support

Group Policy not work in some client machine.

Hello All,
Existing environment is AD 2012. gpupdate /force command does not working in some client machine. And it's occur randomly. Error shown about 15-20% of client machine. Please suggest. Hopefully this time get reply from community.
The Error:
User policy could not be updated successfully. The following errors were encount
ered:
The processing of Group Policy failed. Windows attempted to read the file \\example.net\sysvol\example.net\Policies\{31B2F340-016D-11D2-945F-00C04FB
984F9}\gpt.ini from a domain controller and was not successful. Group Policy set
tings may not be applied until this event is resolved. This issue may be transie
nt and could be caused by one or more of the following:
a) Name Resolution/Network Connectivity to the current domain controller.
b) File Replication Service Latency (a file created on another domain controller
has not replicated to the current domain controller).
c) The Distributed File System (DFS) client has been disabled.
Computer policy could not be updated successfully. The following errors were enc
ountered:
The processing of Group Policy failed. Windows attempted to read the file \\example.net\sysvol\example.net\Policies\{31B2F340-016D-11D2-945F-00C04FB
984F9}\gpt.ini from a domain controller and was not successful. Group Policy set
tings may not be applied until this event is resolved. This issue may be transie
nt and could be caused by one or more of the following:
a) Name Resolution/Network Connectivity to the current domain controller.

Thanks for your reply. basically this error occurs with in same location as well as branch location. i have check event log in AD but not got any specific error. AD health status is ok. AD to AD synchronization also working well. All the client machine running
on windows 7 64 bit and few of them are windows 8.
Please suggest. if you need any event log for analysis i can send you.
Thanks
I recommend you examine the event logs upon an affected client machine. Specifically, look for the surrounding events on that machine (both System, and Application logs), for the hours previous and the hour after.
The time period may vary according to your environment (e.g. what is expected/normal for your environment, your configured GP refresh cycle-time).
e.g., are there network drops, or power drops, or system crashes, restarts at the similar time.
if it's a laptop, is it wireless? Was there a transition from wireless to wired operation?
Is there VPN in use?
If you are able to compare with another machine (I would encourage that), to understand what "normal" looks like in the logs, so that you have some kind of baseline data for comparison.
Other checks, maybe confirm that the machines are updating as required (have the relevant WindowsUpdates etc), and consider if some security/protection/firewall software might be interfering with normal Windows operations.
Also the potential for malware or virus, which can disturb many basic services (ensure a scan is performed and returns clean).
If you have the opportunity for an affected user to contact you urgently when the symptom occurs, check that the gpt.ini file is accessible from their PC.
e.g.: \\example.net\sysvol\example.net\Policies\{31B2F340-016D-11D2-945F-00C04FB
984F9}\gpt.ini
This file is hosted within the replicated SYSVOL share on your DC's, so check that it is accessible.
You might also validate the particular GPO this refers to, and check each of your DC's holds the correct copy of the files for that GPO GUID.
If you open that GPO, and perform a minor change to it (e.g. add a comment), then click Apply, OK, this should cause the GPO contents to replicate an updated version (be cautious, depending upon the nature of that GPO !!!)
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Known Issue – XAudio2 applications built with Windows 10 SDK do not work on Windows 8.x (Windows 10 Insider Preview SDK and tools, April 2015 release)

With this version of the Windows 10 SDK, applications built using XAudio2 will
require XAudio2_9.dll to be on the system, and it is not available for Windows
8.x.

Workaround: Deploy apps using the Windows.Networking.NetworkOperators and Windows.Devices.Sms APIs to a real Windows Phone device that is using an OEM developer account.

Group Chat feature in Office Communications Server 2007 R2 does not work in Windows Server 2008 R2 domains

   Hello to all, there are two confliting articles about this topic:
   1-
http://technet.microsoft.com/en-us/library/upgrade-domain-controllers-to-windows-server-2008-r2(v=ws.10).aspx#BKMK_Whatsnew : this one says that it does not work "The Group Chat feature in Office Communications Server 2007 R2 does not work in Windows
Server 2008 R2 domains". This article was updated in 2013.
   2-
http://technet.microsoft.com/en-us/library/ee692314(office.13).aspx: this other article says that it will function "Office Communications Server 2007 R2 Group Chat will function in a Windows Server 2008 R2 forest". This article was updated in
2010 and was refered by the first one.
   What is the correct support position for Group Chat feature in Office Communications Server 2007 R2 and Windows Server 2008 R2 domains?
   Regards, EEOC.

Hi,
I notice the following sentence in the link below “Office Communications Server 2007 R2, Group Chat will not function in a Windows Server 2008 R2 forest or when Group Chat member servers are joined to a Windows Server 2008 R2 domain.
We know of an issue with changes in Windows 2008 R2 that requires a Group Chat Client and Group Chat Admin Tools hotfix. The Group Chat Client and Group Chat Admin Tools hotfixes are currently scheduled for mid-April 2010.”
http://blogs.technet.com/b/nexthop/archive/2010/11/06/supportability-for-office-communications-server-2007-r2-and-windows-server-2008-r2.aspx
So in my opinion, if you update to the latest version of Windows Server 2008 R2, OCS Server 2007 R2 and Group Chat Client, Group Chat Admin Tools to the latest version, it should work.
However, the best method for you is make a lab to test the problem firstly.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Web Service Client(Console App) not working on Windows Server 2008 R2 Standard Edition

I am trying to consume an ASMX Web Service in a console app, its working fine in Windows 7,Windows Server 2012 Standard,Windows Server 2008 R2 DataCenter,Windows Server 2008 R2 Enterprise, But its not working in Windows Server 2008 R2 Standard Edition which
is the deployment server.
I tried consuming the ASMX web service using Web Reference and Service Reference as well but its not helping. Its throwing up the following error,
Message:There is an error in XML document (1, 331491).
Inner Exception : System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 331491.
The scenario is that i call the web service and it returns me an XML i am not able to receive the XML on Windows Server 2008 R2 Standard Edition.
Please provide suggestions on this I need to resolve this ASAP.

Hi,
This question is better asked here:
http://social.msdn.microsoft.com/Forums/en-US/home?forum=asmxandxml
Experts here are more familiar about it and they can give you more efficient suggestion.
Thank you.

Redirect Printer is not working in windows 2008 R2 Server( Server Running as AD and Terminal Service(both role in single server))

Dear Team
i need solution from Microsoft for the issue;
My infrastructure
- Windows Server 2008 R2 (Role - AD and Terminal Service)- Updated
- Client Machine running with windows 7 pro (Updated)
- Client Using RDP Client to connect Windows 2008 Terminal Session
- All are working fine, but Redirect Printing is not working (Through Windows 7 Pro) ... (HP Laser Jet 1020 plus - attached in Client PC)
- it is working fine from Windows XP
- i was done All terminal setting in both end, also try RDP Login with Administrator User, but issue is not resolve;
What Microsoft can say about the issue;
Thanks & Regards,
VIMAL PRAJAPATI | 09824111686

Have you checked the Print Service log in event viewer?
Here's How.
I have the Microsoft XPS driver on my clients, so I use that fact to my advantage below.
Click Start Button/Administrative Tools/Remote Desktop Services/Remote Desktop Services Manager on the RDSH server
Click the Sessions tab. PC’s are listed Under Client Name by their computer name. Take Note of the corresponding
ID. We will use this to locate the Printer information in the Event Log.
In the Event Log open Application and Services Logs/Microsoft/Windows/Print Service/Admin/ and Find the Event ID 823 entry that has the corresponding ID from the sessions tab you previously noted.
This Event Log Entry is created at Logon and you can only get the session ID when they are logged in.
This tells you what client printer was mapped for the client. The name that appears is the name of the Printer that was set on the client when the printer was installed.
See if you see any errors here.
If you see Event Id 823 with the following message “The default printer was changed to Microsoft XPS Document Writer,winspool,Ne00:. See the event user data for context information.” Twice in a row with no other messages in between, and the first occurs
at the time the user logged in, then their printer was not properly redirected.
You see the Microsoft XPS driver mapped for each session prior to Easy Print redirecting the client machine’s Default Printer.
Since your printer is the HP 1020 I would bet the driver on the client does not work with Easyprint. I would try the the HP Universal Print Driver or the driver for a printer that is very close, like the HP 1018.
Thanks,
Jeremy

Addon not working on Windows Server 2008 OS

Dear Friends,
I have developed an addon in XP and its working fine with XP operating system but it is not working on Windows Server 2008 Standard. Error is "An Attempt was made to load a program with an incorrect format.(Exception from HRESULT: 0x8007000B)".
Regards,
Mahesh.
Edited by: mahesh A on Sep 19, 2009 9:26 AM

Hi,
Since only Windows 2008 SBS is supported with SAP Business One and that Server is available for 64bit Hardware as defined by Microsoft, I guess you should look into that direction.
Regards
Mario

Windows 2008 Group Policy not working in Windows 8.1

Similar Messages

Maybe you are looking for