Re: MobileClient.tcf
- From: "GillRilla" <leeg@xxxxxxxxxxxxxxxx>
- Date: Tue, 4 Apr 2006 12:57:03 -0400
Thanks for the info!
I did a test, which I can explain in detail but suffice it to say that I got
the PC to do a dir of \\remote-server-in-question\SMSClient share using the
PC's system account, and got a access denied. If I do a dir of a different
sms server (secondary or primary) using the PC's system account, I get a
listing. I happen to have 2 servers-in-question that were not setup by our
server team...go figure.
So...I have scoured the remote-server-in-question and cannot find anywhere
where a client PC, using its system account, is getting blocked or denied.
If I find it, I will keep you posted.
Gill
"Kim Oppalfens <MVP>" <Kim dot Oppalfens@google mail.com> wrote in message
news:evZ1Tk$VGHA.4772@xxxxxxxxxxxxxxxxxxxxxxx
5. If the Advanced client network access account fails, we use the client
computer account to authenticate assuming you are in the same forest.
6. If a user is logged we 'll try and use his credentials to download as
well.
If I am not mistaken the actual order is User credentials, computer
account; advanced client network access account.
--
Kim Oppalfens
Telindus Belgium
"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
.
.
- Follow-Ups:
- Re: MobileClient.tcf
- From: Kerwin Medina [MSFT]
- Re: MobileClient.tcf
- Prev by Date: Re: Macintosh
- Next by Date: Re: collections, client installations, and duplicate sms unique id
- Previous by thread: Re: MobileClient.tcf
- Next by thread: Re: MobileClient.tcf
- Index(es):
Relevant Pages
|
