Hello everyone,
I need to package sccm client for windows 7.
I have been provided with ccmsetup.exe, ccmsetup.cab and an i386 folder with source.
We are passing a few parameters to setup.exe ( SMSSITECODE, SMSCACHESIZE ,CCMENABLELOGGING=TRUE). We do get an entry in control panel for configuration manager. But machine is unable to find a management point.
And this property management point should appear in properties tab.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Surely there's no need to package the client, as you can push it from the SCCM Management Console?
Answered 07/14/2010 by: VBScab
Red Belt

Please log in to comment
0
Have you read this? http://technet.microsoft.com/en-us/library/bb680980.aspx

Ian - it's common to add this to the base build, rather than wait for SCCM to do it.
Answered 07/14/2010 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
Well, quite...but I can imagine a few sites - actually, there's no need for me to imagine: the site I'm currently at is like this - where they're migrating from one system to another. Perhaps this is the case for the OP.
Answered 07/14/2010 by: VBScab
Red Belt

Please log in to comment
0
True - I heard the SMS disovery / client distribution could be a bit hit and miss.. maybe it's better with SCCM, hell one day I may end up at a modern site where they use SCCM - or even App-V !! Ahh it's the stuff dreams are made of [;)]

Would be intereting to hear the OP's reason to deploy it - well I say interesting.....

Cheers,
Rob.
Answered 07/14/2010 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
rob just a quick question

when will you finish your cuppa =)
Answered 07/14/2010 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
...when the 'Interview Questions' thread ends.
Answered 07/14/2010 by: VBScab
Red Belt

Please log in to comment
0
Haha can we delete that thread now please? Becoming a bit of a dinosaur!

Ahaaaaaaaaaaaaaa
Answered 07/14/2010 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
i wonder for a long time now, what is written on that cup? :)
Answered 07/14/2010 by: kardock
Second Degree Green Belt

Please log in to comment
0
It's a "Radio Norwich" mug :D

http://en.wikipedia.org/wiki/Radio_Norwich
Answered 07/14/2010 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
I remember, Rob's profile picture instigated one of the first Google searches I ever did inspired by these forums. OK granted it was on Alan Partridge and not say.... Active Setup... but it set the trend...

also, this site brought me LMGTFY... forever grateful for that one.

Back on topic... can you elaborate on the SCCM client inside/ouside the image deal? what do you guys do or prefer? make a package and run after staging? use GPO? trigger from the SCCM server? Guess I'm actually asking what exactly the options are. Reason why I ask is it's been awhile since i've had practical work to do with this kind of deployment tool (since SMS 2003) and we're about to migrate to an SCCM driven environment at my current site (with App-V thrown in too, so I'll keep you posted on that one Rob).

PJ
Answered 07/14/2010 by: pjgeutjens
Red Belt

Please log in to comment
0
The SCCM client belongs in the build, for sure, even if you're not going to use its other features.
Answered 07/15/2010 by: VBScab
Red Belt

Please log in to comment
0
Always glad to hear I'm educating people on the joys of Alan!

And yes we've always had the SMS client in the build. But certainly GPO might be a nice solution to push it out since machine based policies complete before ctrl+alt+del is presented so definately no waiting on discovery via the SMS / SCCM servers.

Cheers,
Rob.
Answered 07/15/2010 by: MSIPackager
Third Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity