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
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