Peter van der Woude

Take a good look at this line and you will find the problem (hint: location of the logfiles).

The idea of using hardlinks is that you only store links to the files, so there is no file copying. AND the best part is that there is only arround 200Mb free disk space needed. If that is still to much then you shouldn't be looking at a hardlink migration, but just a a 'standard' migration with a State Migration Point.

SCCM is 'only' a deployment tool. It can deploy everything you want, but the questions asked during a software installation are outside of SCCM. You need to create a software package (.msi, .exe, etc.) which handles the questions during installation and then use SCCM to deploy the software (silent).

It doesn't matter unless you are going to deploy virtual applications, or deploy an OS to Unknown Computers.

Another option is to 'just' enable it with DISM. This blogpost is initially about something else, but it should get you started: http://www.petervanderwoude.nl/post/Installing-and-enabling-Remote-Server-Administration-Tools-with-ConfigMgr-2007.aspx (keep in mind, with reading it, that it can also be acomplished in a TS with a Run Command Line -step)

How does the collection gets filled? Manual, or with a Query?

WSUS GPO overwrites the Local Policy of the SCCM Client. So just create an OU that doesn't get a WSUS GPO.

Try to Refresh it on the DP

If you don't get an IP-address, then you can't resolve any hostnames. So make sure you get an IP-address, probebly by adding a NIC driver.

On XP and W7?

I need some more information, like how does your environment looks like (servers and sccm-roles) and how do you want to configure the SUP's in it.

What is the SCCM Clients version? I ask this as I've only seen this error with a migration from XP with a SP1 client to W7 with a SP2 client. So make sure that the client is already at SP2 level.

My guess is that you made a little mistake (like a typ-o) in one of the steps or in one of the bat-files. This could easily cause an Incorrect function -error.

Did you extend the AD (for the Site details), or do you provide the Site code with the installation parameters (Client Push)?

It's indeed all because renaming a Site server is not supported. So you don't need to create a Secondary Site, but another Primary Site and make it a child of the existing Primary Site. This will make the data flow to the new Site server. After that remove the connection between the two and you are ready to go. Also don't reuse your Site code, as it can mess things up.

Offline just means that it runs during WinPE, so there is no extra intervention needed.

Don't worry about uninstalling, as that is always possible. Just create a WIM image (with maybe some standard, not often changing, software 'builtin'), deploy standard/ general application at the end of the Task Sequence and deploy the rest of the software based on users or computers.

You need to be more specific... What steps did you performe? What do you see on the client? Does the client even connect with the server? Etc., etc., etc.....

It's good to see that some things that first had to be scripted are now just 'one click', like using hardlinks offline, like adding updates to an image, etc. I just really have to get used to the new interface

You can/ must use USMTUtils for that. Take a look at 'my' blogpost to see how it has to be used: http://www.petervanderwoude.nl/post/Capture-User-Files-and-Settings-Offline-(WinPE)-or-Online-(FullOS)-with-ConfigMgr-2007.aspx

Did you check the UpdatesDeployment.log?

If you are capturing the user state 'Offline' then there is not need to have a user logged on (http://www.petervanderwoude.nl/post/Capture-User-Files-and-Settings-Offline-(WinPE)-or-Online-(FullOS)-with-ConfigMgr-2007.aspx).

I do it using these 'standard' scripts: http://www.petervanderwoude.nl/post/Installing-Software-Updates-via-a-Task-Sequence-in-ConfigMgr-2007.aspx

Just delete the package from the Distribution Point and re-distribute it.

Not totally true, you can also see a mandatory advertisement in RAP, as long as you select Allow users to run the program indepently of assignments in the Interaction tab.