FAQShop.com : Checking for RAS via a Logon Script

Checking for RAS via a Logon Script

I originally set the boundaries on a new SMS rollout to include 10.5.0.0 subnet, as well as 10.6.0.0 subnet here. There then became a need to remove a subnet of the 5 network (for some home dialup users) 10.5.9.0. So I have attempted to include 10.5.1.0, 10.5.2.0, 10.5.3.0, 10.5.4.0, 10.5.5.0 in the boundary settings and removing 10.5.0.0.

All the subnet mask is 255.255.0.0. All my clients on 10.5. subnets are now showing not assigned to site and client removal is taking place. Am I limited to just including 10.5.0.0 as the boundary because of the subnet? Is there a way to exclude the 10.5.9.0 users who authenticate via dialup VPN. Any suggestions would be most appreciated.

SMS goes by the clients subnet mask, which in your case includes the address range you are trying to exclude. Here are some possible solutions:

Move the dial-in subnet outside your B Class.
Use login scripts to install the clients and edit SMSLS.BAT to bypass the script if the client is a certain IP address.
Use CheckRAS from the SMS Support Tools
If you're using Kix, use the @RAS function. @RAS is a Kix macro so look in the macro section of the Kix documentation for details of it's use.