Confused about Autonomous and Replica

-

i understand definition of autonomous , replica i'm confused implementation.

lets have 2 wsus servers.  server1 @ corporate office , server2 @ branch office, server1 upstream, server2 downstream. 

if set server1 autonomous, not propagate approval status etc. server2 need administered locally.  happens if set server2 in replica mode? change relationship?  or changing mode on server2 affect downstream partners of server2?

in other words, if set server1 autonomous, set mode on server2?

i hope question makes sense.

thank clarification.

i understand definition of autonomous , replica i'm confused implementation.

lets have 2 wsus servers.  server1 @ corporate office , server2 @ branch office, server1 upstream, server2 downstream. 

if set server1 autonomous, not propagate approval status etc. server2 need administered locally.  happens if set server2 in replica mode? change relationship?  or changing mode on server2 affect downstream partners of server2?

in other words, if set server1 autonomous, set mode on server2?

i hope question makes sense.

first, must understand terms "autonomous" , "replica" only apply to downstream servers, in example above, server 1 @ corporate office entirely irrelevant question. server 1 known upstream server , question of autonomous vs replica irrelevant.

as matter of pedanticism, upstream server autonomous terms "upstream" inclusive of "autonomous" never spelled out explicitly. likewise, since "autonomous" , "replica" apply downstream servers, formal name "autonomous [downstream] server" , "replica [downstream] server", word "downstream" implied, you'll see these 2 servers referred "autonomous server" or "replica server" , downstream servers.

if @ design of dialog box on upstream server (e.g. server 1 in corporate office), you'll discover impossible access replica checkbox setting in scenario. it doesn't apply. actual implementation procedure goes this:

  1. configure wsus server upstream or downstream.
  2. if downstream server, configure autonomous or replica. default downstream server autonomous, must explicitly enable checkbox configure replica.

so, setting applies downstream server. difference between autonomous server , replica server replica server replicates the target group , update approval information upstream server.

on server 2, in branch office:

  • if choose option "synchronize [wsus] server", define machine autonomous server. autonomous servers not replicate target groups , update approvals. each autonomous server has own independent target groups , update approvals separate may exist on upstream server.
  • if additionally choose suboption "this server replica of upstream server", further define machine replica server and target groups , update approvals upstream server. impossible create target groups or update approvals on replica server.

both servers require local administration. please not misled thinking can put replica server in closet , ignore time. will, certainly, result in failure of replica server @ point in future. thing replica server not require explicit approval of updates deployment clients.

lawrence garvin, m.s., mcitp:ea, mcdba, mcsa
solarwinds head geek
microsoft mvp - software packaging, deployment & servicing (2005-2013)
mvp profile: http://mvp.microsoft.com/en-us/mvp/lawrence r garvin
http://www.solarwinds.com/gotmicrosoft
the views expressed on post mine , not reflect views of solarwinds.



Windows Server  >  WSUS



Comments

Post a Comment

Popular posts from this blog

some help on Event 540

-
does event 540 me distinguish between user , administrator access?    this event generated ypon successfull logon, logon exactly? successful logon on system?   is there other way log administrator access system using event viewer?   thank valuable response   georges hi,   as far know, cannot distinguish between user , administrator access event 540. more information, please refer to:   event id: 540 http://www.microsoft.com/technet/support/ee/transform.aspx?prodname=windows+operating+system&prodver=5.0&evtid=540&evtsrc=security&lcid=1033   events 528 , 540 http://blogs.msdn.com/b/ericfitz/archive/2004/12/09/279282.aspx   regards, bruce this posting provided "as is" no warranties, , confers no rights. please remember click "mark answer" on post helps you, , click "unmark answer" if marked post not answer question. can beneficial other community members reading thread.
Read more

WMI Repository 4GB limit - Win 2003 Ent Question

-
Image
hi there, i've question size limit on wmi repository (being 4gb). if isn't correct place post this, apologies , can let me know wheere post this? i've come across few servers running citrix have reached limit on wmi repository size , need install ibm director agent hw monitoring. during install getting 'out of disk space' errors entered in mofcomp.log: "(mon apr 02 04:10:36 2012.172843) : error occurred while processing item 4: (mon apr 02 04:10:36 2012.172843) : error number: 0x8004103b, facility: wmi description: out of disk space" when error number http://msdn.microsoft.com/en-us/library/windows/desktop/aa394559%28v=vs.85%29.aspx i see this: wbem_e_out_of_disk_space 2147749947 (0x8004103b) disk out of space or 4 gb limit on wmi repository (cim repository) size reached. windows xp , windows 2000/nt:   disk out of space. i'm wondering if there reason why limit set 4gb or can increase needs be? can't seem find reas
Read more

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file

-
Image
hello. we @ step 0 of migration frs dfsr sysvol replication on windows 2008r2 dc. every time run powershell dfsrmig / getmigrationstate says: "unable create dfsr migration log file. error 1307. all domain controllers have migrated global state 'start'. migration has reached consistent state on domain controllers. succeeded." it creates event id 1302 in "dfs replication" event log, explaining error 1307 means: "this security id may not assigned ownder of object ". i already checked space limits, quotas, permissions on c:\windows\debug according microsoft support article unable fix it. although, there new entries added dfsr00095.txt log file despite error. dfsrxxxx file has not been archived .gz format, and, beleive, contains dfsr diagnostics , events. here of latest entries: 20150908 08:47:27.867 11616 sysm  3354 migration::sysvolmigration::getsysvolreadyflag [mig] sysvol ready 20150908 08:47:27.867 11616 sysm   456 migrati
Read more