Migrating a WSUS server to a newer OS with many downstream servers

So here is my situation at my company. Our primary, upstream WSUS server is running Server 2003. It has about 20 downstream WSUS servers, running various versions of Microsoft Server (2003, 2008, 2008 R2 and 2012).
My 1st question:
Is it fine to have the upstream WSUS server OS newer than the downstream WSUS server? I've heard a downstream server's OS doesnt matter, but I wasn't sure about the upstream server.
2nd question:
No matter the answer to question 1, this server will need to be upgraded before July 2015. Can anyone tell me the best way to migrate an upstream WSUS server to a new server? Luckily it's a VM, so it will be fairly to easy to try and rollback if necessary,
but I want to see if anybody else has tried it. We also have about 15 computer groups that I want to keep.
Thanks, Kyle

My 1st question:
Is it fine to have the upstream WSUS server OS newer than the downstream WSUS server?
The upstream server OS should be newer than the downstream server OS. In fact, strictly speaking, an upstream WSUS v3.2 server with a downstream WSUS v6.x server is an unsupported configuration, although it WILL work just fine provided that KB2734608
is installed on the WSUS v3.2 server.
I've heard a downstream server's OS doesnt matter
It doesn't, if all WSUS servers are running v3.2 and at the same patch level.
2nd question:
No matter the answer to question 1, this server will need to be upgraded before July 2015. Can anyone tell me the best way to migrate an upstream WSUS server to a new server?
Yes, the *best* way to do that, which is discussed in this forum at least a few dozen times over the past several years, is to install a NEW server as a replica of the existing upstream server and replicate the upstream server to the new server. Then, reconfigure
the new server as the upstream server, verify the Product Category and Update Classifications selections are correct, and sync with Microsoft. Once you've confirmed the new server is functioning correctly, point the clients and downstream servers to it. Once
all downstream servers and clients have successfully connected to the new server, retire the old one.
I want to see if anybody else has tried it.
Only a few thousand over the past half-dozen years. :-)
We also have about 15 computer groups that I want to keep.
The computer groups will be automatically replicated (just like they are with any other replica server). If you're using Client-Side Targeting, the clients will automatically rejoin in their assigned groups. If you're using Server-Side Targeting, they'll
rejoin in "Unassigned Computers" and you'll have to reassign them. If you have too many computers to manually reassign (one would then ask why you're not using Client-Side Targeting), there's a
free tool at PatchZone.org that will export/import the client computers from the original upstream server to the new upstream server.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Similar Messages

I have a macbook pro can can log into a server, but my new iMac with lion can't even see the server--both are over wifi- how do i get the new iMac to see the server?

i have a macbook pro can can log into a server, but my new iMac with lion can't even see the server--both are over wifi- how do i get the new iMac to see the server?

Without knowing what you have tried please open System Preferences - Sharing - File Sharing and select File Sharing. If you still have trouble you can call AppleCare in the morning when they re-open. You have 90 days of telephone support if you haven't already bought AppleCare.

How to install and migrate a single DC to a new DC with folder redirection.

Greeting's,
I have a Windows Server 2012 running AD services. There is folder redirection enabled to facilitate user's logging in from a different machine and still being able access their personal files. Folder redirection is configured exactly as per following
microsoft document : http://technet.microsoft.com/en-in/library/hh848267.aspx
Even administrators cannot access user files due to ACL's.
I need to migrate from this AD server to a new one, including user files. Old server will be recommissioned for other role. How can I do this seamlessly?
Thank you very much in advance,
Parth D. Maniar

This is how I migrate redirected folders
Remove the setting to move content and set it so that it leaves path when policy is removed
Start a system cmd: psexec -i -s -d cmd
From this system cmd, robocopy all files to new server with permissions
Migrate shares by exporting/importing registry keys support.microsoft.com/kb/125996
Create new policy with new server name -OR- use cname/a host record
And ALWAYS enable "Verify old and new Folder Redirection targets point to the same share before redirecting" GPO

Connections dropped, DNS and server timeouts from new Lenovo with 802.11n

New Airport Extreme, works great with Windows XP machine ethernetted into it, and also with a MacBook with wireless-N.
But my brand new Lenovo T60P with wireless-N is flakey with the Airport. It connects fine with a 100% signal, using the WPA2-PSK / AES setting on the Lenovo (WPA2 Personal security in 802.11n b/g compatibility mode on the Airport). Most of the time it works quite well.
But very frequently (every five minutes?) one of two things will happen: with the signal still registering fine in the taskbar (and in the laptop's wireless "status" utility), it will become unable to locate any website, including google.com, etc., and refreshes of currently-displayed websites yield server timeouts. The browser (firefox) gives a DNS timeout message. The second thing is just your basic dropped wireless connection. It will reconnect by itself after a while.
Any advice is hugely appreciated. It ***** to "upgrade" to headaches! (Ha! the forum software doesn't like a synonym for "vaccuums". Apologies to the nuns at Apple for my potty mouth.)

New Airport Extreme, works great with Windows XP
machine ethernetted into it, and also with a MacBook
with wireless-N.
But my brand new Lenovo T60P with wireless-N is
flakey with the Airport. It connects fine with a
100% signal, using the WPA2-PSK / AES setting on the
Lenovo (WPA2 Personal security in 802.11n b/g
compatibility mode on the Airport). Most of the time
it works quite well.
But very frequently (every five minutes?) one of two
things will happen: with the signal still registering
fine in the taskbar (and in the laptop's wireless
"status" utility), it will become unable to locate
any website, including google.com, etc., and
refreshes of currently-displayed websites yield
server timeouts. The browser (firefox) gives a DNS
timeout message. The second thing is just your basic
dropped wireless connection. It will reconnect by
itself after a while.
Any advice is hugely appreciated. It ***** to
"upgrade" to headaches! (Ha! the forum software
doesn't like a synonym for "vaccuums". Apologies to
the nuns at Apple for my potty mouth.)
What you experienced is not a surprise as 802.11n is not a standard yet and each manufacturer has developed it own "pre-n" version. Right now Apple (base station) will work with Apple (notebooks), Dlink (routers) will work with Dlink (PCMCIA cards), etc.
Lenovo is no different. You can expect 80-90% compatibility, but not 100%. To expect cross-vendor 100% compatibility, you will likely have to wait until 802.11n is "approved" and then the firmware is updated on all devices.

Problems using new version with many sites including facebook...how do I uninstall it NOW

Can't access a multi-list site for my business as a real estate agent...totally screwed up my chats on facebook...I want to uninstall this new version

-> [[Uninstalling Firefox]] - Uninstall your current Firefox
* REMOVE USER DATA AND SETTINGS
* Restart your system
-> Download latest Firefox version from one of these links using some other Web Browser:
* http://www.mozilla.com/en-US/firefox/new/
* http://www.mozilla.com/en-US/firefox/central/
* http://www.mozilla.com/en-US/firefox/fx/
* http://www.mozilla.com/en-US/firefox/all.html
-> [[Installing Firefox]]
Check and tell if its working.

Upstream WSUS Server and Sync

Hello,
Environment : 1. Server 2008 R2 Main Upstream server, hosts update content locally, SQL DB on another system.
2. 2 - Server 2008 R2 downstream servers, host update and sql content locally.
We had our Main Upstream WSUS server crash after applying KB2734608-x64 on a Server 2008 R2 box. Our database resides on a different SQL server on the same domain. When we tried to launch the WSUS interface the mmc console
it would crash. ( MMC has detected an error in a snap in and will unload it. was the error). Looked at the logs and it seems like it could not connect to the database. Anyways after trying many fixes, i decided to re-install WSUS until it got to the point
where it would not allow me to re-install got errors in the log of " InstallWsus: MWUS installation failed ( error 0x80070643: fatal error during installation with other ones like CInstallDriver and CSetupDriver:.....blah blah). I was messing with the
back end database and accidentally deleted it, so i had to restore the latest backup from a month ago ( we typically back on a weekly basis with incrementals, but our backups where failing and we didn't know of this because of a complicated situation
with our client..anyways). My question is once i get the WSUS connected backup what can i expect from the downstream servers in terms of Synchronization? I am assuming initially we will have re approve all updates on the upstream server, before the downstream
server successfully sync? I know i have to recycle the WSUS application pool and reset the update content, anything else? Also any advice on installing that patch? We initially tried to install it because some clients were not reporting into the console properly.
( I know we are on a downward spiral here, any help is appreciated. Will probably end up rebuilding the VM from scratch re-installing WSUS )
Server 2008 - MCITP, Server 2012 - MCSA

Because you had previously attempted the installation of KB2734608 on the WSUS server, it's likely that the database schema has already been modified, making it impossible to connect a downlevel WSUS server to that database. It's unfortunate that you uninstalled
WSUS (probably not necessary and notably complicates the situation), but c'est la vie.
Of course, apparently all that is also irrelevant since you also trashed the back-end database and restored it, so now that database does not have the schema mods imposed by KB2734608.
So, once you get this new WSUS server installed to the restored database, the downstream servers (where I presume you have not yet installed KB2734608 since this update must be installed from the top down) will just keep on truckin'. The only updates you'll
need to approve are the ones that were approved since the last database backup (which hopefully was after you approved this month's Patch Tuesday updates, otherwise you'll likely have a fair amount of work to be done).
Successful synchronization is not a function of the state of the approvals on the upstream server, but if there are any updates NotApproved on the upstream server that were previously approved, a replica server will lose those approvals and client systems
won't get the update until it is (re)approved, the replica resynchronized, and the client performs another detection to (re)find that (new) approval.
I don't know where the "recycle the app pool and reset the update content" stuff is coming from. You're installing a new front-end WSUS server onto an existing database that's already functional. No other actions are required.
As regards successfully installing KB2734608, I suggest thoroughly reading the KB article for starters... TWICE!
First requirement of successfulling installing this update is having a healthy
WSUS server. Not sure why your particular installation failed (installation failures of KB2734608 are pretty rare, as opposed to those encountered by KB2720211), but they're almost always related to existing dysfunctions within the WSUS server.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Migrate WSUS server from 2003x86 to 2008x64, new hardware, use same name and IP address?

Searching through the WSUS forums and reading the TechNET migration documentation, I have bits and pieces of information to make this a smooth transition...I think. I have a plan in mind but
would like the communities input on what I am thinking before moving forward and having it blowup in my face :). <o:p></o:p>
I have the following currently:<o:p></o:p>
A single WSUS 3.0 SP2 server, running on Server Win2003x86, using the default WID (susdb.mdf) on the same server. I have SQL 2005 Express installed on this server as well for other services
but this has no bearing on the WID correct?<o:p></o:p>
What I would like to do:<o:p></o:p>
I have a new server (a much better one) that I would like to move WSUS on to, that will be running Server Win2008x64 (I have to setup first). <o:p></o:p>
Steps that I would like to follow:<o:p></o:p>
1. I will go through and setup this new server with all M$ updates etc... under a new name (ex. wsusnew) and DHCP acquired IP address and then power it down. <o:p></o:p>
2. Get on my current WSUS server and backup all current WSUS settings, groups, DB etc... to a network location for temporary storage. Then power it down.<o:p></o:p>
3. Delete the current WSUS server computer object in AD, DNS entry I will leave because my intension is to give the same IP address to the new WSUS server.<o:p></o:p>
4. Start the new server, static assign the IP address from the old WSUS server to this new server and then change the name of (wsusnew) to the old servers name, which should be ok sense I deleted
the AD object in step 3.<o:p></o:p>
5. After the obvious restart, the new server will have the same name and IP address as the old server. <o:p></o:p>
6. Now that the new server is up (with same settings name/IP as old server), I will then go through and install the WSUS role on the server and restore my WSUS information.<o:p></o:p>
Questions:<o:p></o:p>
1. Step 2 above, is it possible to do this, without making replica servers? I kept reading about this as I was researching doing this, I would rather just copy the DB and folders and simply
put them in-place on the new server.<o:p></o:p>
2. Step 6 above, restoring of the data, what is the proper way to do this in the scenarioI described? <o:p></o:p>
Thank you to anyone who can provide me some information.
Jeff

Thank you for the reply, I will follow and let you know. Proabably be next week sometime before I'm able to try though. So look for a reponse then. Thank you again.
Jeff
OR...
You can use the much more simple, much more reliable, and much more proven method of:
Install new server as a replica of the old.
Replicate.
Configure new server as upstream server.
Point clients to new server.
Turn off old server after all clients have redirected to the new server.
For everybody that has tried the backup/restore the database procedure described above, they have encounted complications of one form or another.
WSUS has a built-in and fully supported comprehensive replication capbility. use it! :-)
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Microsoft MVP - Software Distribution (2005-2012)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

Migrating Netscape Directory Server 4.1 to a new server

Hi,
In the current production environment, we are using Netscape Directory Server 4.1 as the authentication with Siebel CRM system. The server hardware is old and there is a need to refresh the server. As Netscape Directory Server is the only supported/ certified LDAP with embedded functionalities in Siebel Financial Services 6.0.2.300, we are planning to upgrade only the server hardware and migrate all the user information from old server and the new one, with Netscape Directory Server 4.1 remained.
I have studied the Netscape Directory Server 4.1 Deployment Guide and gone through the migration procedures, looks like the procedures are only applicable for migrating Netscape Directory Server to a newer version. There are no specific procedures mentioned for migrating Netscape Directory Server to the new server hardware with the same directory server version.
I am seeking for detailed procedures of migrating Netscape Directory Server 4.1 to a new server hardware with the same directory server. Anyone has done this migration before? I thank you in advance for your valuable feedback.
Sincerely,
Julie

Luckily, I have the technical documentation in hand, which contains all the configuration of the current server. So I need to use "db2ldif" to export the data. I am currently testing on the migration by following these steps:
1. Install the new server.
2. Stop the Netscape Directory Server and Netscape Administration Server services in old server.
3. Copy the slapd-<server_name> folder from old server to a temp location of new server.
4. Take the old server offline.
5. Configure new server to have the exact configuration as the old server.
6. Backup the existing slapd-<server_name> folder in new server, copy the slapd-<server_name> folder from the temp location to C:\Netscape\Server4 directory of new server.
7. Start the Netscape Directory Server and Netscape Administration Server services in new server.
Will try out your suggested method. Thank you so much for your feedback.
Regards,
Julie

Export Approuved Update from old server WSUS to the new WSUS server

Hello,
I want to export all update approuved from one old WSUS server to one new WSUS server
Can you help me please ?
Best Regard

Hi,
>>I want to export all update approuved from one old WSUS server to one new WSUS server ?
There are three steps to exporting and then importing updates:
Make sure that the options for express installation files and update languages on the exporting server are compatible with the settings on the importing server. This ensures that you collect the updates you intend to distribute.
Copy updates from the file system of the export server to the file system of the import server.
Export update metadata from the database on the export server, and import it into the database on the import server. The last section explains how to import exported updates to a replica server
Here is the official solution:
https://technet.microsoft.com/en-us/library/cc720486(v=ws.10).aspx
Best Regards.
Steven Lee 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]

Moving Exchange from old server to completely new server

Hello All,
I hope to get some good pointers here. I currently have Exchange server 2007 SP1 running today. The server is old and the warranty just expired. I have been given permission to buy a new server and migrate to it. I have the new server
up and running with Exchange 07 SP1 installed. I am looking for the best way to migrate and move users from one server, to the new one and decommission the old one. The storage is Are there any special steps I need to take? Do
I need to do any ADPrep to tell AD to use the new server? I've tried looking for a guide or a how-to but all I have found are vague and brief ways to install Exchange server, but not to migrate from one server to a new one. These are two separate
physical servers btw.
edit - I forgot to mention that the exchange store is on a SAN via iSCSI
Thank you,
David

David,
Moving exchange in ten easy steps:
1.Bring up a new server as a new server in the same site. Use a different name for the new server. If you need to move Exchange to another server with the same name, follow the instructions in the Microsoft article “XADM: How to Move Exchange Server to a
New Computer with the Same Name” (http://support.microsoft.com/support/kb/articles/q155/2/16.asp).
2.To move user mailboxes to the new server, start Microsoft Exchange Administrator, click Tools, and select Move Mailbox. You can move all the mailboxes at once, one at a time, or several at a time. In many cases, you can move mailboxes during working hours
because each user is locked out of his or her mailbox only while that mailbox is being moved.
3.Create replicas of the public folders on the new server. When the contents of the folders have been replicated (do wait a little while!), remove the folders from the old server.
4.Create new connectors on the new servers. Change the costs of the old connectors you're replacing to be higher than the new ones, then recalculate routing.
5.Create mail exchanger (MX) records pointing to the new Internet Mail Service (IMS) as appropriate, and change the cost on the old MX record so that it’s higher than the costs on the new records. When you’ve verified that messages are flowing across the
new connectors, remove the old ones, then recalculate routing again.
6.Follow the steps in the Microsoft article “XADM: How to Remove the First Exchange Server in a Site” (http://support.microsoft.com/support/kb/articles/q152/9/59.asp) if the server
you're replacing is the first one in the site.
7.Leave the old server up for a while to give Messaging API (MAPI) clients time to connect to the new server automatically ( the old server provides referrals to the new one). It's true—you don't have to reconfigure MAPI clients!
8.Tell POP3 and IMAP4 users how to reconfigure their clients to point to the new server.
9.If you have a WINS or DNS alias for the old server, point it to the new server.
10.Stop the Exchange services on the old server, then use Exchange Administrator to delete the old server's server object, thus removing it from the site.
I hope that helps you out.
Cheers,
Curt Winter
Certified Microsoft Professional
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied. If you found my post helpful, please mark it as the answer.

NAC using WSUS server

Hi,
Does anyone know how to use WSUS Server in NAC Appliance. I can able to authenticate in the network with the clean access agent. But everytime I used the WSUS requirement it pass through from normal login role to temporarily role for remediation. Im using a WSUS server. So it will lookup to WSUS requirement but the problem I cannot able to remediate using it, I got error message. Do I need to allow some ports in the network to make it work? What ports do I have to open? Please see attachment. Thanks.
Regards,
Richard

Richard,
When you use WSUS with NAC, all the NAC agent does is to tell the Windows Update agent to go update itself. Now it depends on the WSUS setting on the client where it will go to check for updates. If you have it configured for MS servers, it will go talk to them. If you have your clients configured for internal WSUS server, it will check in with them.
Here are details on how to set the registry keys for both scenarios (AD and non-AD)
Non-AD: http://technet.microsoft.com/en-us/library/cc708449%28WS.10%29.aspx
AD: http://technet.microsoft.com/en-us/library/cc720539%28WS.10%29.aspx
HTH,
Faisal

WSUS Server settings and Migrating SCCM 2007 Clients to SCCM 2012 R2

I am in the process of migrating a site from SCCM 2007 to SCCM 2012 R2.
Whilst doing this I came across the following issue:
The first issue is the workstations are woefully out of date, patch and update-wise, some have never had a patch applied as the branch IT staff are building them from the original disk. The policy is set in the SCCM 2007 client to point the machines at
the 2007 WSUS server, which is not set to deliver any updates to 2007 clients and hasn't been for a while. So as soon as the client is installed they lose the ability to get updates from Microsoft and don't get them from the 2007 WSUS server either.
Issue number 2 is the machines are a mixture of hand-built machines to SCCM 2007 delivered images, the SCCM image is patch using offline patching so they are somewhat up-to-date, but the hand-built machines are not and as there is no standardization on
the Microsoft Update client settings, the IT person on-site sets it to whatever he/she feels like, as it makes no difference once the client is installed and the policy applied.
So, when I come to update the client from 2007 to 2012, the following occurs
The Client uninstalls, and the GPO policy settings for Windows Update are removed.
Depending on the setup of the client initially, some machines are then going to Microsoft for their updates (literally 100s) and although the new client is installed the policy update does not fire to update the Windows Update Policy settings, sometimes
for hours after the install finishes. My thoughts are that it just can't run the policy as it is bogged down by patches updating and, in some cases, rebooting and then updating some more.
As a workaround I have had to go in an physically disable Microsoft Update on these machines, which stops the downloading and eventually allows the policy to apply, after which the machine then begins to receive patches from WSUS in a controlled method during
maintenance windows.
I have tried a number of approaches, even setting the Global Group Policy for Windows Update, but the install still removes the keys and basically sets Windows updates back to whatever it was set before the policy was applied and stays that way until the
new client is installed and the Machine policy reapplied. This can be speeded up by initiating it on the client obviously, but that would mean going to each client or using right-click tools on each machine, which is not an option.
What I would like to know is if there is something I am missing from my methods or is it just that I have never been on a site with such out of date workstations built in such different ways.
Any help would be appreciated.

First note that clients do *not* get updates from WSUS in ConfigMgr. The Windows Update Agent (WUA) must point to the WSUS integrated into ConfigMgr (by virtue of having the SUP installed on it) but this is only to make the update catalog/metadata available
to it. Approving updates in WSUS is unsupported for ConfigMgr.
What you've described above is all working as designed although these clients are falling into a gap between the 2007 and 2012 configuration and thus they are reaching out to Windows Update during this gap and installing updates. To prevent this, you
need to disable automatic updates via a domain group policy. This will prevent all automated WUA activity including installing updates from any source automatically. This will not interfere with ConfigMgr Software Updates in any way though.
Jason | http://blog.configmgrftw.com | @jasonsandys

Migrating Crystal Reports Server XI to a new Server

Post Author: david_okeefe
CA Forum: Deployment
Hi,I am trying to migrate an existing Crystal Reports installation from an old server to a new server. To prevent interruption of service, the new server must be able to be online at the same time as the old server (thus it must have a different name). I installed Crystal Reports Server XI and told it to create its CMS database by copying the existing CMS database. Unfortunately, I received an unspecified error ("failed to received first object from source database"). After that, I opted to create a new, default CMS database. I tried using the import wizard to migrate the reports to the new server. The import wizard managed to bring over all of the folders, users, and groups, but not any of the reports. When I looked at the migration log, it gave me an error stating that it could not find the parent folder. I have no real idea how to address this issue. On a related note, I also do not know how to point crystal at the reports repository on the new server. I tried using the Data Source Migration wizard to copy the reports from the old server to the new server. Unfortunately, it didn't appear to register any of the new reports. Given what I have already tried, I am not sure how to proceed.Any help would be appreciated.Thanks,David

Post Author: david_okeefe
CA Forum: Deployment
Hi,I am trying to migrate an existing Crystal Reports installation from an old server to a new server. To prevent interruption of service, the new server must be able to be online at the same time as the old server (thus it must have a different name). I installed Crystal Reports Server XI and told it to create its CMS database by copying the existing CMS database. Unfortunately, I received an unspecified error ("failed to received first object from source database"). After that, I opted to create a new, default CMS database. I tried using the import wizard to migrate the reports to the new server. The import wizard managed to bring over all of the folders, users, and groups, but not any of the reports. When I looked at the migration log, it gave me an error stating that it could not find the parent folder. I have no real idea how to address this issue. On a related note, I also do not know how to point crystal at the reports repository on the new server. I tried using the Data Source Migration wizard to copy the reports from the old server to the new server. Unfortunately, it didn't appear to register any of the new reports. Given what I have already tried, I am not sure how to proceed.Any help would be appreciated.Thanks,David

New WSUS server not showing computers correctly.

Hi All,
I've recently migrated WSUS servers and everything has come intact apart from the grouping. The groups have come over but all the computers are showing under 'Unassigned Computers'.
I've manually removed and added a number of computers but it doesn't show any computers.
Thanks

Hi,
I've only just taken over setting up of WSUS from my colleagues and he's setup computer groups in WSUS and adds the computers to the groups via Active Directory Users and Computers.
The WSUS GPO only sets
Allow non-administrators to recieve update notifications
Allow signed updates from an intranet Microsoft update service location
Configure Automatic updates (Configure automatic updating, Scheduled install day, scheduled install time)
Enabling Windows Update Power Management to automatically wake up the system to install scheduled updates
Specify intranet Microsoft update services location (Set the intranet service for detecting updates, set the intranet statistics server)
Turn on recommended updates via Automatic Updates
Turn on Software Notifications.
Not sure how much help that is!
Well, that is your issue then, if you are using client side targeting with the WSUS Server you will need to place the WSUS Group in the Group Policy. Here is a good technet article to get you started.
http://technet.microsoft.com/en-us/library/cc708574(WS.10).aspx
Hope this helps.

Migrate WWI and Expert Rules to new server

Hello,
Does anyone have any "best practice" document or information related to migrating WWI and Expert rules from an existing server to a new server? The "cookbook" provided in SAP Note for WWI installation does not mention anything regarding "re-install" or "migration.
Thanks in advance.

Hello Thomas,
I do not have a document available for you, but I would do it like this:
Make sure you have the same Word Version installed on both PCs
Make sure the word settings are the same (Trusted Locations / Macro Security etc.)
Make sure you have the same printers/printer drivers and default printer definied on both PCs
Copy WWI and Expert Folder from one PC to the other to the same location
Make sure you have the same PATH Variables defined on both PCs
Makre sure DCOM settings are the same of MS Word and Adobe
If you send PDFs make sure Adobe Reader and the tool you use to create PDFs is installed on both PCs the exact same way
SetUp the Windows Services for EH&S Management Server, WWI and Expert on the new server exactly the way they have been on the old server.
If your new PC has a different OS or newer Office Version I would do a complete new installation via the EH&S Management Server / CGSADM. Make sure to copy your Rules files and Graphics from the old PC to the new PC.
Hope this helps
Mark

Migrating a WSUS server to a newer OS with many downstream servers

Similar Messages

Maybe you are looking for