Fallback Status Point assignment problem
Hello.I have SCCM 2007 SP2 sites hierarchy. AD schema was extended, sites successfully publish information in AD. Boundaries assigned correctly. FSP role is installed. I even see information about FSP in AD:<FSP>
<FSPServer>fspserver</FSPServer>
</FSP> I deploy clients with startup script "ccmsetup.exe /logon SMSSITECODE=AUTO". Clients install OK, but without FSP. In ccmsetup.log I get "A Fallback Status Point has not been specified. Message with STATEID='400' will not be sent." and so on.In SCCM Documentation the process of FSP assignment for my environment: If a fallback status point site system role is installed in a site and the site is publishing to Active Directory Domain Services, running CCMSetup.exe with no command line properties will result in searching for the site's fallback status point in Active Directory. If the client belongs to the same Active Directory forest as the site server's forest, the site's fallback status point will be automatically assigned during client installation.But it does not work! Why? I don't want to explicitly point to fsp with command line parameter FSP=servername, because I have 80 sites and I want tu use 1 script in 1 GPO.
February 2nd, 2010 11:11am
Hi,
Client installation properties stored in Active Directory Domain Services are used only if no other setup properties are specified with any of the following methods:
Manual installation
Provisioning client installation properties using Windows Group Policy
Above is taken from - http://technet.microsoft.com/en-us/library/bb633205.aspxKent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
Free Windows Admin Tool Kit Click here and download it now
February 2nd, 2010 11:24am
I deploy clients with startup script "ccmsetup.exe /logon SMSSITECODE=AUTO". [...]In SCCM Documentation the process of FSP assignment for my environment: If a fallback status point site system role is installed in a site and the site is publishing to Active Directory Domain Services, running CCMSetup.exe with no command line properties will result in searching for the site's fallback status point in Active Directory. If the client belongs to the same Active Directory forest as the site server's forest, the site's fallback status point will be automatically assigned during client installation.
You answered your own question ... and that seconds Kent's statement, too.
February 2nd, 2010 11:39am
Yes, thanks. I figured it out. It's a pity I can't use "/logon" parameter in a simple command line. Either /logon either FSP, not together. Very inconvenient.Have to write a script to check whether or not client is installed, and if not, run "ccmsetup.exe" without any parameters.
Free Windows Admin Tool Kit Click here and download it now
February 2nd, 2010 2:02pm
BTW, the recommendation is to have one FSP for your hierarchy and you should consider using an internet facing server too, particularly if you plan to ever use IBCM. http://www.enhansoft.com/
February 2nd, 2010 3:25pm
Hi, I have question on the this last comment. Based on the http://technet.microsoft.com/en-us/library/bb633164.aspx "Although more than one fallback status point can be installed in a site, clients can be assigned to use only one. "
From what I understand, if I am using FSP for IBCM, I pretty much can only configure the internet-based FSP for those clients. And regardless if they (clients) are on the Internet or Intranet, they'll always use the Internet-based FSP - is that a correct assumption?
This brings me to the second part of the question: I should be able to specify a different Intranet FSPs in sites where the (native mode) clients that will never access the Internet - is that accurate? (I think I just answered my own question but would like
to reconfirm please, if possible).
Free Windows Admin Tool Kit Click here and download it now
October 25th, 2010 5:22pm


