Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SMS and Remote Offices 2

Status
Not open for further replies.

ntgratedweb

IS-IT--Management
Jun 4, 2003
3
US
I am setting up a very large network. I have several remote offices that i want to support using SMS. These offices are on a VPN, but with different subnets (192.168.0.x, 192.168.1.x, 192.168.2.x, etc).
At the central office, where the SMS server is located, all systems have become clients with no difficulty, however, even though some of the software installed automatically on these workstations at the remote offices, the remote office workstations refuse to become clients to the main SMS server. Do I need to put a secondary SMS server at these remote offices in order for the Main SMS server to control these remote office workstations??
I guess I am just curious because I have the subnets for these remote offices listed on the Main Office SMS server, and one would think that, because these are all of a VPN, and the subnets are similar, that there wouldn't be an issue with these remote office workstations becoming clients to the main office SMS server.
Is there something I forget (or ommitted) to do in order to be able to make these remote office workstations clients of the main office's SMS server?? If so, what could i have forgotten to set up??
To assist you in helping me, let me tell you this: I can use VNC from the main office to get to these remote office workstations, and have noted, that when they log in, that they are running the SMS script, and that, in fact, in the control panel, SMS management is listed, however, if I go into the SMS management of these workstations, they do not have the SMS server at the main office listed, in fact, they have no servers listed. Because of this, they are not automatically loading such things as the remote tools or hardware or software profiling tools. Back at the main office, however, I can see these workstations listed i the non-client area. Please help me to figure this out. Thank you.
 
The above response doesn't really help. I am using the standard 192.168.0.x subnet at the Central Office, and 192.168.1.x, 192.168.2.x and so forth at the remote offices. Problem seems similar though.
 
Site4c (part of SMS support tools - may help you out.

======= Overview =======

Site4c puts a given site code into the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\Sites\Forced Sites

When either smsls.bat or smsman is run it does its normal processing and looks up the forced site code on the smslogon share. If present the SMS client is loaded from the forced site. Slownet does apply but site boundaries do not apply. Travel mode does not apply to forced sites (it will assign if it can) but does apply to normal smsls.bat or smsman processing.

In other words, if smsls.bat or smsman is run and ...

- The device is within the boundaries of a SMS site and travel mode is not checked then the device will be assigned to the forced site and the assignable site.

- The device is either within or not within the boundaries of a SMS site and travel mode is checked then the device will be assigned only to the forced site.

- The device is not within the boundaries of a SMS site and travel mode is not checked then the device will be assigned to the forced site. If smsls.bat or smsman is run when the device roams into boundaries of a SMS site then the device will be assigned to the assignable site also.

======= Making use of site4c =======

1. If the device is in the boundary of an SMS site, be sure that a client installation method (e.g. smsls.bat, smsman) will not kick off automatically through logon script or other means

2. Run 20clicln.bat

3. Reboot and ensure that %windir%\ms folder does not exist (delete it if present), and HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS does not exist (delete it if present)

4. Run site4c using syntax: site4c <sitecode>

5. Start client installation

a. If device is outside boundaries of an SMS site in the forced site's target domain you can run smsls.bat from a domain controller where the smslogon share is updated with configuration from the forced site (see notes below).

b. If device is within boundaries of an SMS site in the forced site's target domain then you can:
- Dial into a VPN then assume 5a above, or
- Run ForceCAP (run ForceCAP without parameters for syntax)

6. Turn on travel mode (control panel > systems management > General tab -- check on Mobile Computer box). This setting may autmatically be made if the forced site is configured to automatically turn on travel mode, but doing it manually helps ensure that travel mode is on right away.

If you don't have passthrough Windows authentication rights to the DC (such as a lab in a different domain), first connect to it by UNC and enter the SMS service account information, then you can run smsls.bat from that site. The client continues to operate successfully using the SMS client account so you don't have to re-enter the service account.

Other installation methods such as smsman and capman may used in place of smsls.bat.

- snyderj
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top