You can do that, if you just want the original generic GPOs. You need to create 
a mapping table that maps the attributes of the source domain to the target 
domain.

Cheers
Ken

-----Original Message-----
From: Steven M. Caesare [mailto:scaes...@caesare.com] 
Sent: Thursday, 7 January 2010 2:57 PM
To: NT System Admin Issues
Subject: RE: Windows Update failure

Unfortunately, no... this is a home domain. I have my data dirs on the file 
server and my exchange server backed up, but haven't been backing up the DC's...

I wonder if it's possible to export the GPO's from a new domain and import them 
in..

-sc

-----Original Message-----
From: Ken Schaefer [mailto:k...@adopenstatic.com]
Sent: Wednesday, January 06, 2010 9:45 PM
To: NT System Admin Issues
Subject: RE: Windows Update failure

Do you have a backup? You could restore that to another environment, then use 
GPMC to do an export and then import of your GPO objects.

Cheers
Ken

-----Original Message-----
From: Steven M. Caesare [mailto:scaes...@caesare.com]
Sent: Thursday, 7 January 2010 3:38 AM
To: NT System Admin Issues
Subject: RE: Windows Update failure

Thanks Martin.. that indeed did allow  the system to use MS update.

Now to figure out how to fix my broken/missing GPO files. 

Any thoughts as to how to replace the default GPO objects that should be there, 
such as "default domain controller policy", etc...?

-sc

> -----Original Message-----
> From: Martin Blackstone [mailto:mblackst...@gmail.com]
> Sent: Tuesday, January 05, 2010 10:10 PM
> To: NT System Admin Issues
> Subject: RE: Windows Update failure
> 
> Oh, and you will probably need to restart the automatic updates 
> service afterwards
> 
> -----Original Message-----
> From: Martin Blackstone [mailto:mblackst...@gmail.com]
> Sent: Tuesday, January 05, 2010 7:05 PM
> To: NT System Admin Issues
> Subject: RE: Windows Update failure
> 
> You should be able to remove the offending entries from the registry 
> Windows Registry Editor Version 5.00
> 
> [-
> HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows
> Update]
> 
> [-
> HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows
> Update\AU]
> 
> -----Original Message-----
> From: Steven M. Caesare [mailto:scaes...@caesare.com]
> Sent: Tuesday, January 05, 2010 6:18 PM
> To: NT System Admin Issues
> Subject: RE: Windows Update failure
> 
> Ya I think so. I killed the lnks to the offending GPO object, but now 
> the DC's still have the settings lingering on them, and I don't see 
> the WSUS stuff in the local policy MMC snap in. So I figured I'd edit 
> the old WSUS policy GPO to turn all the settings back to "off",... and

> that's when I found out that the polices don't seem to exist anywhere.
> 
> I hear ya on the time at home thing.... as a matter of fact that's 
> probably why the DC's hadn't been updated for a while and I really 
> hadn't paid attention to the event logs.
> 
> Bad home admin....:(


~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~


~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to