Secondary Site - no management point (DANG IT!)

[itprozj]

Greetings all & thanks in advance,

I have a primary SMS 2003 site within the boudary of a single AD site (Headquaters), & a secondary SMS 2003 site within the boudary of a single AD site (RemoteSite). All machines have been discovered using AD discovery methods & things look pretty good with the exception of this issue.

HEADQUATERS:
HQSDC01 (Win2003sp1)
HQSSMS01 (Win2003sp1 - Site Server/SQL/CAP)
HQSSMS02 (Win2003sp1 - DP/Default MP/RP/SLP)
HQSCLIENT01 (Win2003sp1 - clean install)

<wide open router between - no blocked ports>

REMOTESITE:
RSDC01 (Win2003sp1)
RSSMS01 (Win2003sp1 - Site Server/DP/CAP
RSCLIENT01 (Win2003sp1 - clean install)

< everything is in a single domain >
< senders/addresses/accounts/etc... all defined, Site Status all green
checkmarks)

PROBLEM:
The ccm.log on the secondary site server states "~Default MP: [None]." (so of course my bigger issue is not getting clients installed in the secondary site). When I go & try to define a Default management point in Component Configuration for the secondary site, there are no servers in the "Management point" drop down list (the list drops down, as if there were suppose to be entries, but it's just white space).... it barks at me "Please do not leave this field empty".

What am I missing? My understanding was that a secondary site was suppose to use the primary site for it's default MP automatically.

I ran MPTroubleshooter from RSSMS01 (remote site) & got "testing mpcert http request functionality - failed", though globalstrata states "There is a bug in the MP Troubleshooter so you do not have to worry about the MPCERT HTTP." on tek-tips.com (13 Sep 05 7:50).

Also, how does one "install" a proxy management point? In production I will need to set up 2 secondary sites w/ a proxy management point at each (200+ advanced clients at one of the remote sites). I can't find any documentation on this... does this just mean configure the secondary site as a management point, using itself as default mp & viola it's really, behind the scenes, a proxy MP?

Again, many thanks.

--
Mark Wilson

 

[ncotton]

Have you checked that you have correctly configured the boundaries of the secondary site?

Hope this Helps.

Neil J Cotton
njc Information Systems
Systems Consultant

 

[itprozj]

Ok I have learned how to "install" a proxy MP. One DOES NOT "install" a proxy MP. There is no wizard, there are no installation steps... a SMS admin/engineer >CONFIGURES< a secondary site system to >BECOME< a proxy MP & then a SMS component actually does the install (SMS_MP_Contrl_Manager I believe). Very bad use of terminology by MS & the technical user community. BAH!

Thx Neil for the help. Here's my boundary config:

- 2 AD sites Headquaters (192.168.1.0/24) & RemoteSite (172.16.0.0/16)
- HQSDC01/HQSSMS01/HQSSMS02 192.168.1.2, 3, & 4
- RSDC01/RSSMS01 172.16.1.2 & 3
- Primary SMS "Site Boudary" configured for "Active Directory site" = Headquaters (that's it, no subnets)
- Secondary "Site Boudary" configured for "Active Directory site" = RemoteSite (that's it, no subnets)

I've pulled out just the pertinent info from the ccm.log on the secondary site server for ease.

1) You will see "Defalt MP: [None]. WHY??? Isn't the secondary site suppose to use the primary site management point? (Default managment point IS configured at the primary site, clients are installed/assigned in collections/all systems for primary site clients)
2) You will see "---> No MP shares". I guess this is due to there not being a default MP.
3) You will see "---> No MP shares. Will not push the mobile client to RSDC01". WHY IS IT TRYING TO push client to DC? ("~Install on DC:" is "False).

Cheers,
Mark


<========== ccm.log excerpt ==========>

~Install on DC: False $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 14 10:52:59.615 2006 Central Daylight Time><thread=2044 (0x7FC)>

~Default MP: $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 14 10:53:00.065 2006 Central Daylight Time><thread=2044 (0x7FC)>
~Default MP: [None] $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 14 10:53:00.065 2006 Central Daylight Time><thread=2044 (0x7FC)>
~*** Advanced Security Mode detected *** $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 14 10:53:00.065 2006 Central Daylight Time><thread=2044 (0x7FC)>

======>Begin Processing request: "RSCLIENT01.WAYLAB", machine name: "RSCLIENT01" $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 14 11:01:01.061 2006 Central Daylight Time><thread=2116 (0x844)>
---> No MP shares. Will not push the mobile client to RSCLIENT01 $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 14 11:01:01.061 2006 Central Daylight Time><thread=2116 (0x844)>
Stored request "RSCLIENT01.WAYLAB", machine name "RSCLIENT01", in queue "Retry". $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 14 11:01:01.081 2006 Central Daylight Time><thread=2116 (0x844)>
<======End request: "RSCLIENT01.WAYLAB", machine name: "RSCLIENT01". $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 14 11:01:01.091
======>Begin Processing request: "RSDC01.WAYLAB", machine name: "RSDC01" $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 14 11:01:01.181 2006 Central Daylight Time><thread=2116 (0x844)>
---> No MP shares. Will not push the mobile client to RSDC01 $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 14 11:01:01.181 2006 Central Daylight Time><thread=2116 (0x844)>
Stored request "RSDC01.WAYLAB", machine name "RSDC01", in queue "Retry". $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 14 11:01:01.211 2006 Central Daylight Time><thread=2116 (0x844)>
<======End request: "RSDC01.WAYLAB", machine name: "RSDC01". $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 14 11:01:01.211 2006
======>Begin Processing request: "RSSMS01.WAYLAB", machine name: "RSSMS01" $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 14 11:01:03.310 2006 Central Daylight Time><thread=2116 (0x844)>
---> No MP shares. Will not push the mobile client to RSSMS01 $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 14 11:01:03.310 2006 Central Daylight Time><thread=2116 (0x844)>
Stored request "RSSMS01.WAYLAB", machine name "RSSMS01", in queue "Retry". $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 14 11:01:03.340 2006 Central Daylight Time><thread=2116 (0x844)>
<======End request: "RSSMS01.WAYLAB", machine name: "RSSMS01". $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 14 11:01:03.340 2006

 

[itprozj]

RESOLVED:

I guess I'll just chalk this one up as a noob mistake...

For this particular issue, your secondary site(s) MUST either be:
a. Defined as a subnet or AD boundary in the Primary site's Roaming
Boundaries, as "Designate this boundary as a remote roaming boundary"
OR
b. Configured as a Proxy management point

Of course there are many other reasons that are possible, this one is just
specific to my issue.

Cheers,
Mark