Re: Source \\MP_SERVER\SMSClient\I386 is inaccessible (1326)

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Guy Poulin (GuyPoulin_at_discussions.microsoft.com)
Date: 07/14/04 

Date: Wed, 14 Jul 2004 13:18:03 -0700

Hi,
after i check again the ccmsetup.log on 1 client (who did not get installed) i found something strange, but i don't know where it took it, if you check carefully the log, there is a line were it's write
ccmsetup will use the account 'chelgardeur\_smsinstaller' for network access

but the domain name is not correct, the real domain name should be chlegardeur\_smsinstaller instead of chelgardeur\_smsinstaller, so i check in the push client properties, and the domain name is the right domain, but i delete all the account and recreate it without any more succes, i do a scan in the registry for the value chelgardeur, no luck, i do a search inside every file on the serveur, samething, no luck, i also check the boudary, no luck, so my question is where did if found this domain ? i'm pretty sure than if i can change it to the right domain it's should work

Guy
 

==========[ ccmsetup started in process 2800 ]========== ccmsetup 7/14/2004 3:33:23 PM 648 (0x0288)
Version: 2.50.2726.0010 ccmsetup 7/14/2004 3:33:23 PM 648 (0x0288)
Command line: "C:\WINNT\system32\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 7/14/2004 3:33:23 PM 648 (0x0288)
ccmsetup will use the account 'chelgardeur\_smsinstaller' for network access. ccmsetup 7/14/2004 3:33:23 PM 648 (0x0288)
Config file: C:\WINNT\system32\ccmsetup\MobileClient.tcf ccmsetup 7/14/2004 3:33:23 PM 648 (0x0288)
Retry time: 10 minute(s) ccmsetup 7/14/2004 3:33:23 PM 648 (0x0288)
MSI log file: ccmsetup 7/14/2004 3:33:23 PM 648 (0x0288)
MSI properties: INSTALL="ALL" SMSSITECODE="CHL" ccmsetup 7/14/2004 3:33:23 PM 648 (0x0288)
Source List: ccmsetup 7/14/2004 3:33:23 PM 648 (0x0288)
                  \\LG3\SMSClient\I386 ccmsetup 7/14/2004 3:33:23 PM 648 (0x0288)
Status MPs: ccmsetup 7/14/2004 3:33:23 PM 648 (0x0288)
                  LG3 ccmsetup 7/14/2004 3:33:23 PM 648 (0x0288)
Running as user "SYSTEM" ccmsetup 7/14/2004 3:33:23 PM 1772 (0x06EC)

"Mark Scott [MSFT]" wrote:

> Guy,
>
> You could also try creating a network access account.
>
> Mark Scott [MSFT]
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Guy Poulin" <Guy Poulin@discussions.microsoft.com> wrote in message
> news:4F01A0F9-BD74-40CC-8F2F-FCC392BFE518@microsoft.com...
> > HI,
> > i install Sms 2003 on a fresh server (windows 2003) with sql 2000 and
> > iis6. this server has all the role (Access point, management point, etc)
> > and it seem to work fine, i discover all my client (almost only windows
> > 200 pro) and they populate all the collection correctly, i try to push the
> > advanced client and it seem to work for some and not for other, when i
> > check ccmsetup.log on a client who dosen't want to be upgrade (these
> > client have been in other sms 2.0 organisation before, and the server die
> > so we rebuilt a new server from scratch and rebuilt a new organisation
> > instead of restoring the old one) i always see this error message.
> >
> >
> >
> > Source \\LG3\SMSClient\I386 is inaccessible (1326) (source
> > ccmsetup.cpp:2564)
> > Next retry in 10 minute(s)... (source ccmsetup.cpp:2593)
> >
> > if i try \\LG3\SMSClient\I386 i can see alle the files needed (capinst.exe
> > / ccmsetup.exe / client.msi / smsman.exe) and i'm log with one of the
> > username specify in the
> > Connection account --> client
> > so i'm pretty sure they can access the files, any idea ?
> >
> > Thanks
> > Guy
> >
> >
> >
> >
>
>
>

Relevant Pages

  • Re: SMS 2003 Client Push Problems
    ... In case of push, the network access for the client.msi is done as follows ... If the network access account is provided then that is used to connect to ... then an anonymous network access is made to the Client ...
    (microsoft.public.sms.admin)
  • Re: Source \MP_SERVERSMSClientI386 is inaccessible (1326)
    ... You could also try creating a network access account. ... > and it seem to work fine, i discover all my client (almost only windows ... > client have been in other sms 2.0 organisation before, and the server die ... > so we rebuilt a new server from scratch and rebuilt a new organisation ...
    (microsoft.public.sms.setup)
  • 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: 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: 4 forests-domains, roaming clients, no trusts, not Internet-Ba
    ... distribution points are in that domain, ... Forest2/DomainB, you would create the network access account in DomainA. ... untrusted domains in theis organization is Internet-Based Client ...
    (microsoft.public.sms.setup)