<br><font size=2 face="sans-serif">Here is one for the group.</font>
<br>
<br><font size=2 face="sans-serif">We are still using version 5.13 here
in Saint Paul and plan to upgrade later this fall. However, I'm using
more policies to make changes as we migrate to Active Directory, too. [When
it rains it pours] Anyway. The policies I'm trying to run at
login or on our "every60" task for scoped groups run regardless
if the computer is on our network or at home. Is there a way that
I can tell the policy only to run on our school network? I have network
segments for many of the buildings which are subnets, but I can't seem
to make a network segment that is just on the SPPS network, including subnets.
I get the error "The Network segment entered is not valid"
Example, a single building is 10.22.3.1 - 10.22.6.254, but If I want
to include anything on the SPPS network, I would need 10.1.3.1 - 10.200.6.254,
that doesn't work. I can't enter 10.x.x.x. either. </font>
<br>
<br><font size=2 face="sans-serif">The real question then is how do I keep
policies from running on a computer that is off our network for certain
policies? </font>
<br><font size=2 face="sans-serif">Main issues is the client can't make
the AFP connection. I could go in and check each network segment
I've created under the scope tab, but that is over 80 network segments
to check. I suppose it would work though.</font>
<br>
<br><font size=2 face="sans-serif">I'm expecting to make these types of
policies available over HTTP in version 6 which would take care of this
issue, right?</font>
<br>
<br><font size=2 face="sans-serif">Thanks for the help.</font>
<br>
<br>
<br><font size=2 face="sans-serif">Nathaniel Lindley<br>
<br>
++++++++++++++++++<br>
Learning Systems Specialist<br>
Educational Technology<br>
Saint Paul Public Schools<br>
Saint Paul, Minnesota<br>
nathaniel.lindley@spps.org<br>
phone: 651-603-4929</font>
<br>