Migrate SUS content to WSUS

Two missing steps.

(1) After running 'migratesus /content' you'll then need to either:
(a) run 'migratesus /approve' to restore all of your prior approvals, or
(b) manually approve updates using WSUSAdmin.

(2) One the updates are approved, then the system will issue the 'download'
orders, download any necessary content, and it should also then recognize
content that has already been migrated.

The detailed steps for migration are contained in a special document called
SUStoWSUS.doc (SUS to WSUS Migration Guide) and it available from the WSUS
home page at Microsoft.com.

"beijder" <beijder RemoveThis @discussions.microsoft.com> wrote in message
news:E67CC526-C48D-443D-9A7D-BC6A22061126@microsoft.com...
> We have installed WSUS on the same server where SUS is still active. In
> order
> to have all the CAB (fixes) files moved into WSUS I have ran wsusutil.exe
> migratesus /content c:\sus\content\cabs /log local.log
> This succeeded with the message 900 file migrated.
> However, the WSUS Update screen still shows that 340 updates need to be
> downloaded. And that only 1GB of 10GB has been downloaded.
> It seems that none of the 900 migrated files are available.
> The server has been rebooted after the content migration.
>
> Anyone had the same experience?
>
> Guido
 >> Stay informed about: Migrate SUS content to WSUS 

Thank you for your reaction.

Yes, but as this WSUS server is running in Replica mode I can't
change/configure this.

Guido

"jeutix" wrote:

> Hi Guido
>
> Did you check the language choice?
>
> --
> Greetings
> Udo
>
>
> "beijder" wrote:
>
> > We have installed WSUS on the same server where SUS is still active. In order
> > to have all the CAB (fixes) files moved into WSUS I have ran wsusutil.exe
> > migratesus /content c:\sus\content\cabs /log local.log
> > This succeeded with the message 900 file migrated.
> > However, the WSUS Update screen still shows that 340 updates need to be
> > downloaded. And that only 1GB of 10GB has been downloaded.
> > It seems that none of the 900 migrated files are available.
> > The server has been rebooted after the content migration.
> >
> > Anyone had the same experience?
> >
> > Guido
 >> Stay informed about: Migrate SUS content to WSUS 

Hello Lawrence,

Thank you for your reaction to my post.
The WSUS server I'm talking about is a replica server, on which SUS
was already running, also in replica mode.
I can't approve updates on a replica server.

I have installed the WSUS replica server as described in the "Step-by-Step
Guide to Migrating from Software Update Services to Windows Server Update
Services"
Published June 3, 2005 by Tim Elhajj and Sean Bentley from Microsoft.

As far as I can see it lacks detailed info on this item in a replica
environment.
At this moment (approx. 15 hours after I installed the first replica server
and tried to
"import" the CAB update files into the local database) the status of the
replica server
is that all updates are up-to-date. Approx. 400 updates are in the database.
(Which should have been 900+ I guess).
I have the feeling that the import step (wsusutil migratesus /content...)
has succeeded, but that WSUS has nevertheless synchronised (during the night)
all updates (downloaded) from the "master". The network card statistics show
me that more then 10GB has been transferred since the installation of WSUS
replica.

I need to setup more replica's on sites with lower bandwith spec's so it
would be
great if the migration of the local (SUS) content would work.

Guido

"Lawrence Garvin" wrote:

> Two missing steps.
>
> (1) After running 'migratesus /content' you'll then need to either:
> (a) run 'migratesus /approve' to restore all of your prior approvals, or
> (b) manually approve updates using WSUSAdmin.
>
> (2) One the updates are approved, then the system will issue the 'download'
> orders, download any necessary content, and it should also then recognize
> content that has already been migrated.
>
> The detailed steps for migration are contained in a special document called
> SUStoWSUS.doc (SUS to WSUS Migration Guide) and it available from the WSUS
> home page at Microsoft.com.
>
> "beijder" <beijder RemoveThis @discussions.microsoft.com> wrote in message
> news:E67CC526-C48D-443D-9A7D-BC6A22061126@microsoft.com...
> > We have installed WSUS on the same server where SUS is still active. In
> > order
> > to have all the CAB (fixes) files moved into WSUS I have ran wsusutil.exe
> > migratesus /content c:\sus\content\cabs /log local.log
> > This succeeded with the message 900 file migrated.
> > However, the WSUS Update screen still shows that 340 updates need to be
> > downloaded. And that only 1GB of 10GB has been downloaded.
> > It seems that none of the 900 migrated files are available.
> > The server has been rebooted after the content migration.
> >
> > Anyone had the same experience?
> >
> > Guido
>
>
>
 >> Stay informed about: Migrate SUS content to WSUS 

Hello Guido,

that's my problem, too. Exactly. I'd really like Microsoft to find some
better way of migrating the SUS. My experience on more than one
replica-server is that

1. If you don't synchronize the replica-server with the upstream one and
just try to run wsusutil migratesus - it doesn't do anything, because it
finds no metadata.

2. If you do synchronize (or you run wsusutil export on the upstream server
and then wsutil import on the replica), it just imports the metadata,
reports success and starts synchronising the contents from the upstream
partner.

3. At that moment you can run wsusutil migratesus. Then it reports some
amount of files to have been synchonised (different amount on different
servers, varying from 6 to 900 in my environment, though the SUS-Server were
synchron, I can't explain it). But it doesn't matter at all, the WSUS goes
on downloading the contents from the upstream server till it has everything.

That' really a problem for us having a lot of remote sites with functioning
SUS and beeing now made to download the complete content from the central
site once again over the busy lines.

I would as minimum appreciate the solution with wich one could export /
import not only the metadata, but the contents, as it was possible (at any
rate with some handwork) with SUS.

Alexander


"beijder" <beijder.DeleteThis@discussions.microsoft.com> schrieb im Newsbeitrag
news:E67CC526-C48D-443D-9A7D-BC6A22061126@microsoft.com...
> We have installed WSUS on the same server where SUS is still active. In
> order
> to have all the CAB (fixes) files moved into WSUS I have ran wsusutil.exe
> migratesus /content c:\sus\content\cabs /log local.log
> This succeeded with the message 900 file migrated.
> However, the WSUS Update screen still shows that 340 updates need to be
> downloaded. And that only 1GB of 10GB has been downloaded.
> It seems that none of the 900 migrated files are available.
> The server has been rebooted after the content migration.
>
> Anyone had the same experience?
>
> Guido
 >> Stay informed about: Migrate SUS content to WSUS 

Why updating at all?

I've just installed another VM and installed the WSUS from scratch. Then
adjusted the GPO, let the machines come in. And only those updates who are
needed, I approve for download and install. All other updates already done by
SUS appear as not needed.

After that I've shutdowned my old VM-SUS.

--
Greetings
Udo


"Alexander Lerner" wrote:

> Hello Guido,
>
> that's my problem, too. Exactly. I'd really like Microsoft to find some
> better way of migrating the SUS. My experience on more than one
> replica-server is that
>
> 1. If you don't synchronize the replica-server with the upstream one and
> just try to run wsusutil migratesus - it doesn't do anything, because it
> finds no metadata.
>
> 2. If you do synchronize (or you run wsusutil export on the upstream server
> and then wsutil import on the replica), it just imports the metadata,
> reports success and starts synchronising the contents from the upstream
> partner.
>
> 3. At that moment you can run wsusutil migratesus. Then it reports some
> amount of files to have been synchonised (different amount on different
> servers, varying from 6 to 900 in my environment, though the SUS-Server were
> synchron, I can't explain it). But it doesn't matter at all, the WSUS goes
> on downloading the contents from the upstream server till it has everything.
>
> That' really a problem for us having a lot of remote sites with functioning
> SUS and beeing now made to download the complete content from the central
> site once again over the busy lines.
>
> I would as minimum appreciate the solution with wich one could export /
> import not only the metadata, but the contents, as it was possible (at any
> rate with some handwork) with SUS.
>
> Alexander
>
>
> "beijder" <beijder.RemoveThis@discussions.microsoft.com> schrieb im Newsbeitrag
> news:E67CC526-C48D-443D-9A7D-BC6A22061126@microsoft.com...
> > We have installed WSUS on the same server where SUS is still active. In
> > order
> > to have all the CAB (fixes) files moved into WSUS I have ran wsusutil.exe
> > migratesus /content c:\sus\content\cabs /log local.log
> > This succeeded with the message 900 file migrated.
> > However, the WSUS Update screen still shows that 340 updates need to be
> > downloaded. And that only 1GB of 10GB has been downloaded.
> > It seems that none of the 900 migrated files are available.
> > The server has been rebooted after the content migration.
> >
> > Anyone had the same experience?
> >
> > Guido
>
>
>
 >> Stay informed about: Migrate SUS content to WSUS 

I don't think you can migrate SUS into a replica server, either.

The replica server is going to have to synchronize and update from the
upstream WSUS server.

"beijder" <beijder RemoveThis @discussions.microsoft.com> wrote in message
news:BF9C2872-AF7E-4FD5-A2B0-3EEE15CEEBF6@microsoft.com...
> Hello Lawrence,
>
> Thank you for your reaction to my post.
> The WSUS server I'm talking about is a replica server, on which SUS
> was already running, also in replica mode.
> I can't approve updates on a replica server.
>
> I have installed the WSUS replica server as described in the "Step-by-Step
> Guide to Migrating from Software Update Services to Windows Server Update
> Services"
> Published June 3, 2005 by Tim Elhajj and Sean Bentley from Microsoft.
>
> As far as I can see it lacks detailed info on this item in a replica
> environment.
> At this moment (approx. 15 hours after I installed the first replica
> server
> and tried to
> "import" the CAB update files into the local database) the status of the
> replica server
> is that all updates are up-to-date. Approx. 400 updates are in the
> database.
> (Which should have been 900+ I guess).
> I have the feeling that the import step (wsusutil migratesus /content...)
> has succeeded, but that WSUS has nevertheless synchronised (during the
> night)
> all updates (downloaded) from the "master". The network card statistics
> show
> me that more then 10GB has been transferred since the installation of WSUS
> replica.
>
> I need to setup more replica's on sites with lower bandwith spec's so it
> would be
> great if the migration of the local (SUS) content would work.
>
> Guido
>
> "Lawrence Garvin" wrote:
>
>> Two missing steps.
>>
>> (1) After running 'migratesus /content' you'll then need to either:
>> (a) run 'migratesus /approve' to restore all of your prior approvals,
>> or
>> (b) manually approve updates using WSUSAdmin.
>>
>> (2) One the updates are approved, then the system will issue the
>> 'download'
>> orders, download any necessary content, and it should also then recognize
>> content that has already been migrated.
>>
>> The detailed steps for migration are contained in a special document
>> called
>> SUStoWSUS.doc (SUS to WSUS Migration Guide) and it available from the
>> WSUS
>> home page at Microsoft.com.
>>
>> "beijder" <beijder RemoveThis @discussions.microsoft.com> wrote in message
>> news:E67CC526-C48D-443D-9A7D-BC6A22061126@microsoft.com...
>> > We have installed WSUS on the same server where SUS is still active. In
>> > order
>> > to have all the CAB (fixes) files moved into WSUS I have ran
>> > wsusutil.exe
>> > migratesus /content c:\sus\content\cabs /log local.log
>> > This succeeded with the message 900 file migrated.
>> > However, the WSUS Update screen still shows that 340 updates need to be
>> > downloaded. And that only 1GB of 10GB has been downloaded.
>> > It seems that none of the 900 migrated files are available.
>> > The server has been rebooted after the content migration.
>> >
>> > Anyone had the same experience?
>> >
>> > Guido
>>
>>
>>
 >> Stay informed about: Migrate SUS content to WSUS