Domain group validation hangs during ECC 6.0 install on windows server 2008

Hello to the group.
We are installing ECC 6.0 R3 on a windows server 2008 system (with SQL 2008) and the install is hanging in the user/group creation steps. Specifically, the install is able to create a group at the domain level but hangs when it tries to verify that group.
What's funny is the system is able to create two local domain groups without any issues.
Have any of you run into this same issue? We've tried updating sapinst and restarting the install process using a known good domain admin account (we are also creating a ticket to SAP support).
Thanks for any help!
J. Haynes

> This is actually a Domain based install.
ok
> So far after 12 hours the install is still hung. So we are looking at both network and issues with the AD related DLLS.
You can doubleclick on the orange icon (the sapinst backend process) next to the clock on the desktop and scroll down. There you may find a hint why it's taking so long.
Maybe you have a wrong/missing DNS server entry so the server is unable to find the domain controller, maybe the firewall is enabled and blocking asynchronous answers.
Markus

Similar Messages

Error during ECC 6.0 installation on Windows Server OS

Hello Experts,
I am having trouble installaint ECC 6.0 on windows server 2008 with MS SQL. I was half way through the installation and encountered an error. Hence i am trying a fresh installation however I get an error message " Cannot determine parameter SAPGLOBALHOST from default profile " . I have deleted registry entries for the previous installations, yet I am unable to proceed. Please help . Have cheked the forum bue haven found any inputs other than http://forums.sdn.sap.com/thread.jspa?threadID=1040931. This has not been of much help.

Hi Venkata,
Default profile.........
SAPDBHOST = BR0137
dbms/type = mss
dbs/mss/server = BR0137
dbs/mss/dbname = ERP
dbs/mss/schema = erp
j2ee/dbtype = mss
j2ee/dbhost = BR0137
j2ee/dbname = ERP
SAPSYSTEMNAME = ERP
SAPGLOBALHOST = BR0137
rdisp/bufrefmode = sendoff,exeauto
SAP Message Server for ABAP
rdisp/mshost = br0137
rdisp/msserv = sapmsERP
rdisp/msserv_internal = 3903
SAP Central Service Instance for J2EE
j2ee/scs/host = br0137
j2ee/scs/system = 02
j2ee/ms/port = 3902
SAP Message Server for ABAP
SAP Central Service Instance for J2EE
SAP Message Server for ABAP
SAP Central Service Instance for J2EE
SAP Message Server for ABAP
SAP Central Service Instance for J2EE
login/system_client = 001

SAP ECC 6 EHP 4 on WIndows Server 2008 MSSQL 2008

Hello,
Our's is a new installation and I am applying the required patches in the Development system. The Kernel release is 701 and our SAP_APPL version is 600. Please let me know what will be the impact of upgrading SAP_APPL to 604.The upgrade will require the EHP installer which will ask for the XML file prepared from Solution Manager. This will involve the upgrade of all the components. Is it mandatory to do the upgrade of SAP_APPL?
Kindly send in some suggestions.

Successfully upgraded to SAP_APPL 604

Window SBS server 2008 and window server 2008 R2 on the same domain

Hi all,
I am a person only work for linux system. Recently i work for my company that using microsoft technologie. So i have a lot of trouble. Could you please help me and below are my big troble that i have met:
In my system, i have the first window SBS server 2008 run on our domain. However my organization growth up and we have more than 150 users and mailbox of exchange server 2007. So i do not want to use my sbs server 2008 anymore.
I am going to install a window server 2008 R2 64 bit and join it into the same domain with sbs server 2008. It will be replicate the username, dns, OU and group policy...After that i will tranfer FSMO role to new server and i will demote then remove the
sbs server.
My boss say that i should not use this solution because window server sbs can not run with any other kinds of window server 2008 (R2, standard, enterprise...) and it will automatically shutdown the main server after a couple of days.
Someone have experience can help me. I am so confuse now

Maybe this will also help to better understand the steps involved:
Transition from Small Business Server to Standard Windows Server
http://blogs.technet.com/b/infratalks/archive/2012/09/07/transition-from-small-business-server-to-standard-windows-server.aspx
Migrating away from SBS 2011
http://social.technet.microsoft.com/Forums/en-US/07c58cc4-7d6d-419a-b1a0-439c2cc0c48d/migrating-away-from-sbs-2011?forum=smallbusinessserver
Migrating from SBS 2008 to Windows Server 2012 R2 (NOT Essentials and with NO Exchange)
http://social.technet.microsoft.com/Forums/en-US/1276d2d3-a8f2-4786-82f3-4308a2affb11/migrating-from-sbs-2008-to-windows-server-2012-r2-not-essentials-and-with-no-exchange?forum=smallbusinessserver
And remember, as long as you don't move the PDC to one of the new DCs, you can leave the SBS 2008 up indefinitely. But I would remove Exchange 2007 off it right away once I've migrated the mailboxes and public folders, otherwise
you will get yourself into an Exchange coexistence scenario which is much more complex to configure and support because of the CAS differences, changing the URLs on the old one to "legacy.domain.com," getting a new UC/SAN cert with the correct
names on it, and more. Believe me, you really don't want to coexist them. The only time I've coexisted Exchange versions is during large migrations, such as 500 or more. Otherwise, I just migrate the mailboxes over a weekend and get it done with.
Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights.

Upgrading windows server 2003 domain controller to windows server 2008

Hello friedns :
We have a company with about 2000 users , and two windows server 2003 domain controllers , one of them acts as a primary domain controller , and the other acts as secondary domain controller , all the FSMO s are on the primary DC ,we have decided to upgrade all of our servers from windows server 2003 to windows server 2008 , the first step is to upgrade the domain controllers to windows server 2008 , our domain controllers are so sensitive and has to be active 24 hours a day , i have stress upgrading it to windows server 2008 , what is the best solution to upgrade it with no risk ?
( i have an opinion but i am not sure and i dont have any guide about it , i want to install a windows server 2008 and promote it as an additional domain controller to the windows server 2003 DC and the transfer all the FSMOs to it , and then promote the first domain controller !!! is that possible ? if yes , is there any guide about it? )
If there is a guide available for it please let me know . (Specially if there is a tip & trick)
thank you guys.
Network is my LOVE

Hi,
This TechNet online article might be helpful for you.
How to Upgrade Domain Controllers to Windows Server 2008 or Windows Server 2008 R2
http://technet.microsoft.com/en-us/library/ee522994(WS.10).aspx
For your convenience, I have list some general steps for your reference.
Since the following operation have potential damage to Active Directory database, it is highly suggested that you'd better perform a full backup of Active Directory (System State) firstly. Also it is better to test the following procedure in a similar lab environment first.
General Steps:
=============
1. Verify the new server's TCP/IP configuration has been pointed to the current DNS server.
2. Make the new server become a member server of the current Windows Server 2003 domain first.
3. Upgrade the Windows Server 2003 forest schema to Windows Server 2008 schema with the "adprep /forestprep" command on old server.
Please run the "adprep.exe /forestprep" command from the Windows Server 2008 installation disk on the schema master. To do this, insert the Windows Server 2008 installation disk, and then type the following command:
Drive:\sources\ADPREP\adprep.exe /forestprep
4. Upgrade the Windows 2003 domain schema with the "adprep /domainprep" command on old server.
Please run the "adprep.exe /domainprep" command from the Windows Server 2008 installation disk on the infrastructure master. To do this, insert the Windows Server 2008 installation disk, and then type the following command:
Drive:\sources\ADPREP \adprep.exe /domainprep
5. Insert Windows Server 2008 Installation Disc in the new server.
6. Run "dcpromo" on new server to promote it as an additional domain controller in existing Windows 2003 domain, afterwards you may verify the installation of Active Directory.
Please refer to:
How to Verify an Active Directory Installation in Windows Server 2003
http://support.microsoft.com/kb/816106
7. Verify the new server's TCP/IP configuration has been pointed to current DNS server.
8. Enable Global Catalog on new server and manually Check Replication Topology and afterwards manually trigger replication (Replicate Now) to synchronize Active Directory database between 2 replicas.
Please note: It will some time to replicate GC between DC, please wait some time with patience.
9. Disable Global Catalog on the old DC.
10. Transfer all the FSMO roles from the old DC to the new DC.
Please refer to:
How to view and transfer FSMO roles in Windows Server 2003
http://support.microsoft.com/kb/324801
11. Verify that the old DNS Server Zone type is Active Directory-Integrated. If not, please refer to:
How To: Convert DNS Primary Server to Active Directory Integrated
http://support.microsoft.com/kb/816101
Note: Active Directory Integrated-Zone is available only if DNS server is a domain controller.
12. Install DNS component on new server and configure it as a new DNS Server (Active Directory Integrated-Zone is preferred). All the DNS configuration should be replicated to the new DNS server with Active Directory Replication.
13. Make all the clients change TCP/IP configuration to point to new server as DNS.
14. You may configure TCP/IP on all the clients, or adjust DHCP scope settings to make them use the new DNS server.
Please note: It is a good practice to make the old DC offline for several days and check whether everything works normally with the new server online. If so, you may let the old DC online and run DCPROMO to demote it.
Hope it helps.
Regards,
Wilson Jia
This posting is provided "AS IS" with no warranties, and confers no rights.

How to restrict users working on Windows 7 clients from accessing Windows Explorer and other systems in the network through Group Policy with a domain controller running on Windows Server 2008 r2

Dear All,
We are having an infrastructure setup of around 500 client computers managed through group policy.
Recently the domain controllers have been migrated from Windows Server 2003 to Server 2008 R2.
Since this account requires extremely strict environment, we need to figure the solution for restricting the users from access anything locally.
It would be great if you can assist me with the following query.
How to restrict users logged on Windows 7 clients from accessing Windows Explorer and browsing other systems in the network through Group Policy with a domain controller running on Windows Server 2008 r2 ?
Can we disable Network Tab on the left hand pane ?
explorer.exe is blocked already, but users are able to enter the Windows Explorer by clicking on the name which is visible on the Start Menu.

>   * explorer.exe is blocked already, but users are able to enter the
>    Windows Explorer by clicking on the name which is visible on the
>    Start Menu.
You cannot block explorer.exe when you do not replace the shell - the
desktop you see effectively IS explorer.exe...
Your requirement sounds like you need a custom shell:
http://gpsearch.azurewebsites.net/#2812
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 :))

Windows Server 2012 Group Policy Block USB Storage devices @ User Level Not getting applied on a Domain Client machine with Windows Server 2008 R2. Why?

Hello,
I have a Windows Server 2012 R2.
I have configured the Group Policy on it to block the usage of USB - Storage Devices @ user level on the client machines. It works properly for my Windows 7 client machines but it's not working on one of the machine having Windows Server 2008 R2 installed
on it (this machine is also a domain client in the same domain).
I will really be thankful if anyone can suggest some solution to this issue.
Please feel free to write back in-case I have missed anything obvious to be shared.
Thanks!
-Vinay Pugalia
If a post answers your question, please click "Mark As Answer" on that post or
"Vote as Helpful".
Web : Inkey Solutions
Blog : My Blog
Email : Vinay Pugalia

Hi,
Any update?
Just checking in to see if the suggestions were helpful. Please let us know if you would like further assistance.
Best Regards,
Andy Qi
TechNet
Subscriber Support
If you are TechNet
Subscription user and have any feedback on our support quality, please send your feedbackhere.
Andy Qi
TechNet Community Support

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

The cluster resource could not be found-SAP ECC on Windows Server 2008 MSCS

Hi,
I'm installing SAP ECC 6.0 on Windows server 2008 MSCS Cluster. As mentioned in the guide, i've created a service and added a resource.
I was able to successfully configure the DB installation and cluster configuration. But when I start the ASCS installation, the installation fails when it tries to create system folders with the following error.
Error when sharing file system export (share) saploc : The cluster resource could not be found
I'm using a user with domain admin access and also a member of the local administrators group. I've even tried to install using the domain administrator user but still the problem exists.
Can anyone please let me know where am I going wrong ?
NB: The host on which I'm installing is not a domain controller but it is a member of a domain.
Regards,
Varadharajan M

Yes Krishna,
I've not created any shared folders manually and I've used the "Use domain of current user" option.
Actually SAPINST has created the usr and sap folder in the SAP drive (say E: drive) which is a clustered disk. The name of that clustered sidk is "Clustered Disk 1". I could able to open up the shared directories available in that SAP virtual host by issuing
<SAPGRP>. I don't know where am I going wrong:( I've also opened a call with a SAP and waiting for their reply.
Regards,
Varadharajan M

Windows Server 2008 R2 SP1 RDS hang and stop responding new rdp session. Already connected session also hang as well

We have a Windows Server 2008 R2 SP1 RDS supporting many ThinClients, mostly using a mandatory profile on a Windows 2003 R2 AD environment
at the moment of the hang what we experienced was:
New RDP sessions got stucked in the legend "Iniciando" (we have the spanish MUI).
Systems Events shows a lot of Warnings:
The Group Policy Client Side Extension Group Policy Shortcuts may have caused the Group Policy Service to terminate unexpectedly. To prevent further failures in the Group Policy
Service, this extension has been temporarily disabled until after the next system restart. Group Policy settings managed by this extension may no longer be enforced until the system is restarted. The vendor of this extension should be contacted if this issue
recurs.
and after that a lot of this errors:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CryptSvc service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the NlaSvc service.
The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.
timeout (30000 milliseconds) was reached while waiting for a transaction response from the Schedule service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the gpsvc service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the BITS service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SessionEnv service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CertPropSvc service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the IKEEXT service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the iphlpsvc service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SessionEnv service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the iphlpsvc service.
During the problem we ping DC and Network Share where Profile and Document Redirection resides and they were working OK (we also did a
\\server\HomeUsers and we reached it without problem)
Only reseting the server worked, Any Ideas of what could be causing this ?? Best Regards
Federico Giampietri Latamsupport IT Infrastructure Services

Hi Clarence,
Today we experienced the problem again,
Users can’t login to RDS, but now they got stucked at “"Please wait for the Group Policy client”;
System log events recorded the following errors again:
timeout (30000 milliseconds) was reached while waiting for a transaction response from the Schedule service.
timeout (30000 milliseconds) was reached while waiting for a transaction response from the sessionenv service.
timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.
timeout (30000 milliseconds) was reached while waiting for a transaction response from the Wuauserv service.
timeout (30000 milliseconds) was reached while waiting for a transaction response from the BITS service.
timeout (30000 milliseconds) was reached while waiting for a transaction response from the CertPropSvc service.
What path do you suggest to investigate further?
Thanks a lot!
Federico Giampietri Latamsupport IT Infrastructure Services

Install Active Directory Domain Controller on Windows server 2008 enterprise, dont login on Sql Server 2008 R2

I install Active Directory Domain Controller on Windows server 2008 enterprise and dont login on Sql Server 2008 R2. Before install ADDC, I have logon SQL Server 2008r2 Success, After when i install ADDC is don't logon on SQL Server 2008r2 -->not success.
I have uninstalled ADDC but i still can't login on SQL server 2008r2.
please help me. it is very very disaster!
I think is loss account SQL server 2008r2!

Hello,
I stronly recommend you post the detail error message to us while you try to connect to SQL Server instance, it's useful for us to do further investigation.
Microsoft recommends that you do not install SQL Server 2008 R2 on a domain controller, there are some limitations:
You cannot run SQL Server services on a domain controller under a local service account or a network service account.
After SQL Server is installed on a computer, you cannot change the computer from a domain member to a domain controller. You must uninstall SQL Server before you change the host computer to a domain controller.
After SQL Server is installed on a computer, you cannot change the computer from a domain controller to a domain member. You must uninstall SQL Server before you change the host computer to a domain member.
SQL Server failover cluster instances are not supported where cluster nodes are domain controllers.
SQL Server Setup cannot create security groups or provision SQL Server service accounts on a read-only domain controller. In this scenario, Setup will fail.
On Windows Server 2003, SQL Server services can run under a domain account or a local system account.
So, I would suggest you try to open up Windows Services list and changed the account for SQL Server service.
Regards,
Elvis Long
TechNet Community Support

Windows 7 64-bit Pro not connecting to SQL Server on domain Windows Server 2008 R2 Standard

I am upgrading computers from Windows XP Professional to Windows 7 Professional but I have a problem getting one of the stock control software programs we use to connect to our SQL Windows Server 2008 R2 Standard from the new Windows 7 computers.
Our computers are connected to a domain and so is the SQL Server. The Windows XP computers allows each standard domain user to log on and connect to the SQL Server via the stock control software program.
But on the Windows 7 Pro computers standard domain users can't connect to the SQL Server but the domain administrator accounts on the same Windows 7 Pro computers can connect to the SQL Server via the stock control program.
I have setup the server alias, server name and port number via the SQL Server Client Network Utility (cliconfg.exe) so I know this isn't the problem as it works when I am logged on as domain administrator.
It seems to be something to do with domain user permissions and Windows 7 Pro. There seems to be a change from Windows XP Pro to Windows 7 Pro that doesn't allow standard domain users to connect to an SQL Server. But I can't find anything about this and
can't workout how to fix it except to make all the users domain administrators which is obviously not a good thing to do. So basically I I think I need to create a group policy that allows the users to connect to the SQL Server but I have no experience doing
this and don't know where to begin.
Thanks for all you guys help and I hope someone can provide me with the solution to this problem.

Hi,
Was there any message?
Please run the stock control software as Administrator to check if it was caused by UAC.
If it could run as administrator, please add the standard domain user to local administrator.
Karen Hu
TechNet Community Support

ECC 6/MS Windows Server 2008/SQL Server 2008 Upgrade

I am working with a client who wishes to do an ECC upgrade from ECC 5 to ECC 6. They also wish to upgrade the Op System from Windows Server 2003 to Windows Server 2008; and the database from MS SQL 2005 to MS SQL 2008.
My proposal is to Upgrade ECC, then the Op System then the DB in each environment before moving forward. We would do the first upgrade in Sandbox to determine timing, issues, etc. We would create a production support path to be used during the project, then start the upgrades Dev-QA-Prod.
The client has said that this is a risky approach and that SAP recommends a 2 step process, that is, upgrade ECC 6 thru all environments and then go back and do the Op Sys and Db upgrades afterward.
In my mind my approach is less risky as we will ensure each environment is clean and functioning smoothly before moving forward; there is less intrusion to the end user; testing is only accomplished once in each environment. The actual production build would be split over 2 weekends, app upgrade first then op sys and db.
The assistance I need to understand isu2026.does SAP have a recommendation in this case? I have not seen anything that says not to do the single step process I am recommending.
Thanks for any support you can provide.

Hi,
If SAP is recomending that is because They recomends not to "mix" upgrades with any other process like Heterogeneous system copies, DB upgrades, etc. In fact this is in the upgrade guides. But I think like some others here has already writen, that you could upgrade and change OS and SQL server in two different steps but in the same process so the downtime will be longer but it will be only one.
Of course this will depend on how long your upgrade downtime will take because usually the upgrade could take 7 hours more or less, post upgrade tasks, export task (R3load), change OS and SQL server if not using different HW, import task and post copy tasks.
What is the maximun downtime your client is ready to tolerate? If you have a whole weekend beginning from friday afternoon and ending Monday morning probably you will have enough time to do all in one weekend but again, it will depend on your tests. Why don´t you talk to your client and tell them if they have new HW already for this project to do a Prod copy in one of those servers as part of the whole project and take the times you will need. Then with that in perspective you could decide what approach is better.
With some upgrades done under my belt to different clients I don´t assure anything until I do a test upgrade including all changes (os or DB) necesary to finish time schedules, then with that in mind then we can redefine the way we will use and we make that clear before the beginning of the project. I always tell them that it is better to do a test like this if they don´t have much available downtime, the project will take longer but for sure the Production downtime will be shorter.

Windows Server 2008 R2 Domain Controller NOT logging EventID 4740

EventID 4740 (account lockout) is not being logged to the event viewer. When searching through the security log there are none to be found. Having accounts locked out and no logging is driving me nuts. Hope someone has run into this before. This is what
i have checked thus far.
>Windows Server 2008 R2 Domain Controller
>Verified the following GPO settings are set and correct:
>Computer Configuration\Windows Settings\Security Settings\Local Policies\Audit Policy\ all are set for Success & Failure
>Computer Configuration\Windows Settings\Security Settings\Advanced Audit Configuration\Logon/Logoff) is set for Success and Failure
>Powershell command Get-Eventlog -log Security -InstanceId 4740 returns no results which makes sense since there are no entries in the security log file.
>No 4740 entries in the netlogon.log debug file
AD and the LockoutStatus tool show the account is locked out but i still have nothing in the logs.
Anyone have any ideas? From everything i can find online , it appears i have everything set properly.
Thanks, Chico

Hi Chico,
I suggest you try to enable this group policy below:
Computer Configuration\Windows Settings\Security Settings\Local Policies\Audit Policy\Audit account management
More information for you:
Missing 4740 EventID's
http://social.technet.microsoft.com/Forums/windowsserver/en-US/c9871d72-7439-46b5-98e6-a7fadfa6ff28/missing-4740-eventids?forum=winserversecurity
If you have multiple Domain Controllers, check this event on other DCs, too.
Please feel free to let us know if there are any further requirements.
Best Regards,
Amy Wang

Group Policy Administrative Templates not applying on Windows XP SP3 - Windows Server 2008 R2

I have a Windows 2008 R2 domain with windows 7, and Windows XP SP3 client workstations.
I have a group policy to deny all access to removable storage in policies/administrative templates/system in user configuration (actually its in the computer configuration as well)
The problem is the policy is having no effect on the Windows XP machines. It works perfectly on Windows 7 machines.
Group policy in general is working on the Windows XP machines, as I can successfully map drives, push out scheduled tasks, and push out printers. (All preferences I know and I have GP Preferences client side extensions installed).
Its almost like the windows XP machines can't "understand" the admin templates from Windows Server 2008 R2.
Do I need to install something on the windows XP machines? What could be the problem?

> Its almost like the windows XP machines can't "understand" the admin
> templates from Windows Server 2008 R2.
Simply read the "supported on" of these settings... Vista and above
required.
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 :))

Domain group validation hangs during ECC 6.0 install on windows server 2008

Similar Messages

Maybe you are looking for