Fallback Status Point will not install via New Site Server wizard
I am trying to configure a site system as a fallback status point on a secondary site installed to a VM with Server 2008 Standard and SCCM R3. I used the ConfigMgr console to install the secondary site, and then installed R3 manually. I am trying to install
the FSP via Central Site > Site Systems. I am able to complete the wizard and add the site to the Site Systems group, but the FSP install doesn't appear to be happening. Neither of the logs (fspmsi.log and smsfspsetup.log) referenced on technet are showing
up. Is there something I've missed or somewhere I can find a log to give me a better Window into what's going on? I've installed all the prerequisites listed here (http://social.technet.microsoft.com/Forums/en/configmgrsetup/thread/f0f667e2-2a63-4783-85fd-105c4dfee348)
and have disabled Windows firewall.
Thanks!
June 20th, 2011 7:59pm
Hello - In most of the org FSP is installed on central site and the FSP is used for all the other sites.
Did you check the communication between the sites? Have you configured the address that connects to the sites? Other components (MP,DP etc...) are installed on the secondary site?
Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually
answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
June 20th, 2011 9:46pm
You will do fine by having a single FSP at the central site.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund
June 21st, 2011 12:14am
My understanding is that installing a FSP on the same system with other roles isn't recommended by MS - is that incorrect? Does it not really matter? I am using Native Mode and would like to support IBCM in the near future.
Either way, there appears to be something going on that's prohibiting my central site from installing new roles on remote sites - I have another server I'm trying to use as a DP, among other things. I haven't been able to find any way to confirm whether
or not this role is installing successfully either. Please bear with me as I'm new to ConfigMgr - I basically have a book and a few Hyper-V servers to work with and I'm trying to figure out how to get this thing running.
Sender addresses are configured, and I was able to install secondary sites remotely - it's just the role install that seems to be gummed up somewhere. Is using the new site server wizard from under the central site hierarchy the correct method?
Free Windows Admin Tool Kit Click here and download it now
June 21st, 2011 12:31am
My understanding is that installing a FSP on the same system with other roles isn't recommended by MS - is that incorrect? Does it not really matter? I am using Native Mode and would like to support IBCM in the near future.
Either way, there appears to be something going on that's prohibiting my central site from installing new roles on remote sites - I have another server I'm trying to use as a DP, among other things. I haven't been able to find any way to confirm whether
or not this role is installing successfully either. Please bear with me as I'm new to ConfigMgr - I basically have a book and a few Hyper-V servers to work with and I'm trying to figure out how to get this thing running.
Sender addresses are configured, and I was able to install secondary sites remotely - it's just the role install that seems to be gummed up somewhere. Is using the new site server wizard from under the central site hierarchy the correct method?
June 21st, 2011 12:31am
FSP (http) should not be placed on a site in native mode (https).
The computer account of the siteserver has to be member of the local admins on remote systems in order to install roles there.Torsten Meringer | http://www.mssccmfaq.de
Free Windows Admin Tool Kit Click here and download it now
June 21st, 2011 10:02am
So even with an infrastructure running in native mode, I should set up an FSP in mixed mode? Would it still be able to communicate with my central site which is set up for native mode, and be set up as a secondary site?
I have already added the site server computer account to the local admins group on both servers, but the problem still persists. Is there a log file somewhere on the central site that would indicate why the remote role install is failing?
June 21st, 2011 5:44pm
There is no "FSP in mixed mode". It's a site system that only accepts http connections. See
http://technet.microsoft.com/en-us/library/bb694178.aspx and
http://technet.microsoft.com/en-us/library/bb680900.aspx for details and http://technet.microsoft.com/en-us/library/bb680830.aspx ("How
to Create a Fallback Status Point in Configuration Manager").
Torsten Meringer | http://www.mssccmfaq.de
Free Windows Admin Tool Kit Click here and download it now
June 21st, 2011 6:29pm
Ok - I was confused when you said that an FSP should not be placed on a site in native mode. Are you saying it should not be placed on a site concurrently with other roles if using native mode?
The second article is what I have been using for reference when trying to install. The steps under "To create the fallback status point on an existing site system server" complete, and the wizard finishes, but then nothing seems to happen as far as the install
goes. It's really confusing because I was able to install the ConfigMgr secondary site remotely, and everything seems to be communicating as far as I can tell in Sender.log. It's just that something is getting in the way of adding a new role. There is an ISA
server in the environment, could that be getting in the way somehow, even though it apparently let the secondary site install through?
June 21st, 2011 6:40pm
Looks like I was wrong about the distribution point not installing. The distribution point is indeed installed and working. I just blew away the fsp server and started over from scratch, but I'm getting the same result. The fspmsi.log on the FSP server is
not being created, nor is the smsfspsetup.log being created on the central site. I have met all prerequisites listed in this article: http://blogs.technet.com/b/configmgrteam/archive/2009/02/18/the-fallback-status-point-prerequisites-verification-and-troubleshooting.aspx
I'm pretty stuck here - I have had no luck finding a log that gives me visibility into what is happening or failing to happen when I run the wizard to add a site role. Could anyone point me to one, or offer an idea as to what to try next?
Free Windows Admin Tool Kit Click here and download it now
July 2nd, 2011 6:59pm
See sitecomp.log on the site where you initiated the installation of the FSP from.
The FSP logfiles should be on the server where the FSP will be located.
Plus there are also status messages available.Torsten Meringer | http://www.mssccmfaq.de
July 3rd, 2011 3:07am