Re: Secondary Site Not Generating ccr

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi, Kerwin,
Yuhoo...
It seems to be generating the CCRs now after adding the permission to the
client installation share...
Thank you so much for the tip... :-)

Now...if only I could go around those systems that reports "Access Denied"
on the CCR... :-( We have some systems that does not have the account we
use in the system for local admin tasks. To make it tougher, some systems
also have Sygate Enterprise Firewall software on them... grrrrr :-) But
it's another story :-) I know there're other ways to have the client
installed. I just have to be more creative :-)

Oh...may I ask another question?
I have already posted this but no reply yet.
I have configured a secondary server which is actually a part of a different
domain (DOM2). I believe I was able to successfully configured it. However,
I cannot discover the clients using the subnets used in DOM2. If I use their
AD containers, I am able to see some system, but mostly server :-( .
Would you have any recommended steps to follow to successfully discover
these secondary clients from a different domain? I have added both domains
in the DNS entries on the servers as well.

Again, thanks so much for your assistance...

Have a very nice day !

Newbie



"Kerwin Medina [MSFT]" wrote:

When ccmsetup is started on the client by push install (CMM), ccmsetup will
always download from the SMSClient share of the site that did the push
install.

So, for all your sites that you intend to use for push intallation using
your network access account, should grant that network access account
permissions to their SMSClient shares.

Note also that targetted push (where you do a righ-click on a collection and
select the client install operation) only works with primary site servers
because it requires access to the SMS database.

"SMS Newbie in the Block" <SMSNewbieintheBlock@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message news:39DDE200-5882-49F5-BEC5-FCF4DC1E4B6A@xxxxxxxxxxxxxxxx
Hi, Kerwin,

Thank you very much for the response.

I have done the steps this morning and confirmed that the network access
account has permission on the "Client" share (RWX)...

Just to confirm...the systems are in the secondary site...
Do I need to to this on the secondary server or primary server, or both?
I believe the default if I do the "Install Client..." from the SAC is the
Primary's....Would I be correct on this one? If yes and I wanted them to
use
the one for the secondary, whats the best way to do that..and is it
recommended?

I will let you know how goes it...

Thank you so much again for your response.

:-) Newbie


"Kerwin Medina [MSFT]" wrote:

That account will be used to access the share, so if it has no
permissions
yet, you need to add it. And btw, its the "network access account" (set
on
the software dist settings) - not the "client installation account".

"SMS Newbie in the Block" <SMSNewbieintheBlock@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message
news:0EF3DD39-68BB-473B-81B8-894EFFAB9E4D@xxxxxxxxxxxxxxxx
Hello, Kerwin,

Can I add the client installation account to the client installation
share
permission?

Just want to make sure :-)

Thanks for the response...

"Kerwin Medina [MSFT]" wrote:

Try creating a network access account that has permissions to the site
share. Then retry the push.

"SMS Newbie in the Block"
<SMSNewbieintheBlock@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message
news:92731F09-AEBA-45B1-BAC1-DA16B14254CB@xxxxxxxxxxxxxxxx
I have same, exact symptom...
If I do a manual CCR on the secondary server, it installs the
client.
However, if I do the "Install Client..." via the SAC, no luck :-(

Client Push Installation is configured with valid installation
account
and
member of the local admin group of the target system.

The installation files are shared and has the default permissions...
Do I need to add the <Domain>\Domain Users account for Read access
to
this
share for it to work? Or should the default ones be sufficient.

The secondary servers are configured as a Management Point for each
respective sites. Anything I shoulkd double-check on the Management
Point
configuration maybe?

Thanks for any input one can provide :-)

Newbie

"tmyhlfgr" wrote:

thanks for your help! Turns out the share on the server where the
installation files are had gotten moved. The ccr was being
generated
but
the
client wasn't installing because the files we inaccesible.

"David Tyra" wrote:

Do you have Client Push Installation method enabled? Do you have
a
discovery method enabled that is creating DDRs? You can look at
ddm.log
on the secondary site server to see if any DDRs are being
processed
and
if so, why CCRs are not being created for the discovered
resources.

Regards,

David Tyra











.

Relevant Pages

  • RE: MS Software Update Service
    ... and approve the patches before releasing them to your clients. ... Automatic Update client) ... Doesn't patch SQL Server, Exchange, Office, etc. ... distributed through Active Directory software installation, ...
    (Focus-Microsoft)
  • Re: Small Biz Design
    ... After we installed SBS 2003 successfully on the server box, the Client ... >When we setup SBS 2003 server using installation disks, ...
    (microsoft.public.windows.server.sbs)
  • Re: How do I reinstall setup.exe file for clients in server?
    ... I rebooted the server and afterwards I looked at the event log for specific ... interesting because our sbs 2003 installation is supposed to be 32-bit! ... And where in the wizard will there be the option just to install the Client ...
    (microsoft.public.windows.server.sbs)
  • Re: How do I reinstall setup.exe file for clients in server?
    ... Did you go to the Control Panel> Windows Small Business Server 2003 and click on the Change Remove button? ... interesting because our sbs 2003 installation is supposed to be 32-bit! ... And where in the wizard will there be the option just to install the Client ...
    (microsoft.public.windows.server.sbs)
  • Re: Client Push Installation Security (Micorosft pls assit)
    ... > %machinename%\account for the Client push installation. ... > Network Access, can i specify a Domain Users rather than a Domain Admin ... >> Software Installation account: ...
    (microsoft.public.sms.swdist)