[sccm 2007] Problems deploying client

[Ric_]

I'm struggling to get the SCCM client puched out to my machines

 

AFAIK, everything is setup correctly. I have SCCM 2007 R2 installed on Server 2008 R2. All the pre-requisites passed and I have even updated the AD schema

 

I've even read books and tutorials and everything!

 

All the CCMSetup log files are displaying the same messages...

 

 

Any and all ideas would be welcomed.

[Ric_]

Surely somebody else has had a similar problem!!!

[ZeroHour]

I am pretty sure I had a similar issue but I cant remember what it was yet.

Notice though:

StatusCode at WinHttpQueryHeaders: 404

Are you remembering to add distro points and update them for the client install package?

[mounters]

Have you got SCCM 2007 SP2 installed?

How are you trying to push the client out?

Have you set up Client Installaiton Methods under Site Settings?

 

As an aside I do appreciate the site code , is it annoying you that much

[Ric_]

@ZeroHour: I assumed that you didn't need to update the distribution point to push the client out... it's not mentioned anywhere in that book you lent me!

 

@mounters: You spotted that eh? A large stick might be making contact with the thing soon!!!!!!!!!!

[mounters]

Everything has to be put on a distribution point with SCCM.

 

It's really not that bad, went SCCM over the summer and once you've got your head round a few things (like making sure everything has a distribution point, advertisement, etc) then it's all pretty good.

[10101010]

is it something to do with the size of the cache size you need to set on the client

[ZeroHour]

Ric I will be down your way this week so you may just need to pay me to consult

I accept cash (aka beer vouchers) or even just beer....

[Ric_]

Ric I will be down your way this week so you may just need to pay me to consult

I accept cash (aka beer vouchers) or even just beer....

 

If you could bring your largest hammer, I would be grateful.

 

I've read the deployment chapters of your book and those at System Center Configuration Manager 2007 and nothing mentions distro points. It basically says "click this, click that, pop these details in and bam you're done!"

[Ric_]

OK... I thought I'd post exactly what I did (or near enough exactly)...

 

1. Installed Server 2008 R2

2. Re-named computer and joined the domain

3. Installed SQL Express 2005

4. Installed pre-requisites for SCCM

5. Ran 'simple install' of SCCM with SP1

6. Ran upgrade to SCCM R2

7. Configured Boundary

8. Configured Client Push Installation

9. Configured AD System Discovery and told it to run immediately

10. Picked a client from the 'All Systems' collection and told it to install the client.

11. Started scratching my head and cursing it for not working!

12. Updated schema (in case the schema update would kick things into life - it didn't!)

 

From all the instructions I have, this is the correct procedure for installing SCCM and performing a 'client push' installation. You're supposed to do this for all your client machines and it will then tell you oodles of information and allow you to do whizzy stuff.

 

AFAIK, the Software Distribution Point isn't needed until you start deploying 'other' software packages to the clients (although I do know that you can use the Distribute task as an alternative method of client deployment).

 

Have I done something clearly wrong here?

[markberry]

Ric,

 

I've just spoken to our techie who did the install. He has said you have to have a distribution point and you have to put the client on it. Update distribution points, then create an advertisement for the client.

 

He's also suggest you check the account that SCCM is running under especially that used for client push.

[azrael78]

Hmmmmm

 

We didn't have this particular issue - I did pretty much the same as you except used SQL 2005 (not Express).

 

We updated the schema first, prior to installing.

 

Once you configure client push - and then run discovery, it should automagically push the client out to the PCs it discovers - assuming it can.

 

Check to ensure you have a network access account and a client push account setup so that it has local admin rights on the pcs you want to install the client.

 

It also may not install the client on ALL PCs in AD - particularly if you have old computer accounts or the PCs are turned off... (as I'm finding out... hurrah)

 

I too - like the site code, that's what I set my first SCCM install to - it was a test install so I wanted to give it a totally unique site code we would never use in production

 

HTH,

 

Az