SUS Server SP-1

[Thomas]

Hi there.

I trying to create a manual content distribution
pointinstead of using a SUS server (offline network).

I have a SUS SP-1 server which to take the content from
(it get's its own content directly from WindowsUpdate).

If you look in the SUS_Deployguide_sp1.doc you'll notice
under the headline "To create a manual content
distribution point" that it's not written very user-
friendly, and I actually think it's wrong.

Here's the info. from the document:
---
1. Confirm that IIS is installed.

2. Create a folder named \Content

3. Copy all the files and folders under the \Content\cabs
directory from the source server running SUS to the
\Content directory on the server with the manually-created
content distribution point:

4. Copy the following files under the VROOT of the default
web site
<root of the SUS Web site>\Aucatalog1.cab
<root of the SUS Web site>\Aurtf1.cab
<root of the SUS Web site>\approveditems.txt

5. Create a VROOT called "Content" and point to
the "\Content\Cabs" directory

--

Notice number 3 which I understand as:
Copy the whole contents of "content/cabs" (all files &
folders beneath the cabs folder) to the root of the manual
content distribution point "content".

Like this: \content\cabs\*.* -> \content

This dosn't really make sence if you look at number 5:
You can't create a VROOT to point to the cabs folder when
there is not cabs folder (remember we took the contents of
the cabs folder and put it in the root folder called
content).

When you read the "In other words" beneath these five
points you'll see:

---
In other words, you are taking content from the \Content
folder on a server running SUS that can connect to the
Internet, and copy this content to the manually-created
content distribution point. Remember to copy the complete
\Content directory.
---

Point: The two desciptions of what to do dosn't seem to be
the same, and I havn't really made this work - since you
can't really tell if it's working because it takes about
22 hours for each check to go through from the client to
the server - it's a long time to test different methods.

Anyone make it work ???

[Don Cottam [MS]]

Yep, looks like there's an error in those instructions. The Content VROOT
should simply point to the \Content folder. I'll double-check with the
owner of the deployment guide and see if we can get this corrected.

On your second point, which server are you pointing the client machines at?
You can kick-start a detection cycle by deleting the
HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto
Update\LastWaitTimeout registry key and then restarting the AU service.
Detection should occur about 5~10 minutes after you do that.

Don [MS]

"Thomas" <t.br...@dk.intrum.com> wrote in message
news:074901c2e895$00f8c630$a101...@phx.gbl...

[Thomas]

The clients point to the Manual Content Distribution
Point's IP adress like this: http://192.168.1.2

>.
>

[Don Cottam [MS]]

That is a point of misunderstanding. Setting up a manual distribution point
allows you to sync a SUS server that otherwise couldn't sync (because it's
not connected to the Internet), but since the manual distribution point is
*not* an actual SUS server, pointing the clients at it won't result in
anything happening.

You need to install SUS on a server that your clients can access, and then
point that SUS server at the manual distribution point in order to sync, and
then point the clients at the SUS server, instead of at the manual
distribution point.

Don [MS]

"Thomas" <t.br...@dk.intrum.com> wrote in message

news:06c301c2e94d$69b37f40$a101...@phx.gbl...

[Thomas]

But it should be possible to do this:

Install a SUS server, sync with WindowsUpdate.

Copy the files created by the SUS server (as described in
the white papers) to an offline network server which has a
SUS server and IIS 5.0 installed.

Make the clients get updates from the offline SUS server.

Right?

>.
>

[Don Cottam [MS]]

Actually setting up an offline SUS server requires copying more files that
just creating a manual distribution point, which is why the whitepaper
suggests (a) create a manual distribution point and, (b) sync SUS server
against it. The sync process does much more than copy just the cabs: for
one thing it extracts the contents of the aucatalog*.cab to the correct
location on the SUS server, and then loads all those text files (dictionary
objects) into SUS server memory so that it "knows" what updates are
available. It is possible to set up a SUS server without this sync process,
but it's much more detailed than simply creating a dist point.

Don [MS]

"Thomas" <t.br...@dk.intrum.com> wrote in message

news:15d201c2ee16$42872700$a001...@phx.gbl...

[Thomas]

OK. Thanks for the answer :)

Is there any place where I can download og read
instructions to how to do this?

In my case it's not possbile to get the server on the
online network due to security risks.

I've read the white paper and I thought it was possible
but I don't remember reading anything about how you're
supposed to do this..

>.
>

[Don Cottam [MS]]

There isn't any current documentation how to do it because it's not one of
the scenarios that SUS 1.0 was designed to support. I'm pretty sure it can
be done though, without too many problems. I've done it before (just
experimenting) and I think at least one other person here in the newsgroup
also did it. I'll try to put together a quick document with the steps,
although please understand that it won't be "officially" blessed by the
product team.

Don [MS]

"Thomas" <t.br...@dk.intrum.com> wrote in message

news:3c2e01c2f39d$f175f610$a601...@phx.gbl...

[Thomas]

That's so kind :-)

Thank you! for your time, effort and possitive attitude.

>.
>