Re: MobileClient.tcf

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

I have pushed 1200+ clients from the primary site without the access
account.

Gill


"Lalli" <Lalli@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AE1F00CC-2D1A-4934-8B46-DC2D97BB09F8@xxxxxxxxxxxxxxxx
Hi Gill

The Advanced Client Network Access account cannot be blank if you want to
be
able to push the client no matter what security mode you use.

What happens in the background when you push the client is:
1. The SMS admin console creates a Client Creation Record on the site
servers CCR inbox, this triggers the Client Config Manager
2. Client config Manager on the SMS site server connects to the target
admin$ share using the Remote Installation account, copies ccmsetup.exe
and
MobileClient.tcf to \\targetsystem\admin$\system32\ccmsetup
3. Client config Manager on the SMS site server the creates a bootstrap
service on the target that simply runs ccmsetup.exe, after this is done
the
Site server has finished it's part
4. ccmsetup.exe uses the Advanced Client Network Access account to connect
to the \\server\SMSClient share

The Advanced Client Network Access account only needs to be a member of
domain users for this to work

Lalli

"GillRilla" wrote:

I am using Advanced Security, so those fields are blank. Again, if I use
the
MobileClient.tcf file from a different site server (Primary or Secondary)
the client downloads fine. There seems to be a security issue

Gill

"Lalli" <Lalli@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:68712610-A601-4D48-923F-9DF6A9A2B07B@xxxxxxxxxxxxxxxx
Hi, this file contains the Advanced Client Network Access account and
my
guess is that it has been entered incorrectly on this site, there is no
verification against the real account in Domain/AD, the account details
in
Domain/AD could have been changed or it might be locked out.

Lalli

"GillRilla" wrote:

I have a site where clients seem to have a problem with this file. Can
this
file be re-generated?

When my clients try to attached to the server specified in the
MobileClient.tcf file, it says that the \\server\SMSClient\i386 is
inaccessible. If I replace the MobileClient.tcf file with one from a
different site server and restart ccmsetup, it installs the client
fine.

Gill


.






.

Relevant Pages

  • Re: 4 forests-domains, roaming clients, no trusts, not Internet-Ba
    ... a forest other than the site server's forest, it would probably work, but it ... The only potential ambiguity that exists is the branch distribution point ... you would create the network access account in DomainA. ... client requires that there are no trusts. ...
    (microsoft.public.sms.setup)
  • Re: MobileClient.tcf
    ... PC's system account, ... where a client PC, using its system account, is getting blocked or denied. ... The Advanced Client Network Access account cannot be blank if you want to ... Client config Manager on the SMS site server the creates a bootstrap ...
    (microsoft.public.sms.setup)
  • Re: MobileClient.tcf
    ... PCs system account) being allowed to access the share. ... The TCF file that does not work points to the client share that is ... The Advanced Client Network Access account cannot be blank if you want ... Client config Manager on the SMS site server the creates a bootstrap ...
    (microsoft.public.sms.setup)
  • Re: 4 forests-domains, roaming clients, no trusts, not Internet-Ba
    ... Communications across forests work in Configuration Manager 2007 if the ... Account appears to be for Client to Server communication. ... Which seems to indicate that a client from untrusted Forest/Domain 1 can ... it also states "The Network Access account is never used to run the ...
    (microsoft.public.sms.setup)
  • Re: Client push installation is still failing on windows XP SP2 cl
    ... What does it say in your ccm.log from the site server you are pushing from. ... Have you setup the Advanced Client Network Access Account and the Client ... >>> Both RPC and remote registry are running on the clients. ...
    (microsoft.public.sms.admin)