Regular latop returns

[Gatt]

Anyone know of a way to force staff members with laptop to being said laptop back into school every 14 days?

 

They are all Windows 7 Ent, and using KMS, but the problem with KMS is that the expiry date is 180 days, and I cannot find a way to alter it...

 

Is there any other way that I can effectivly "Lock" the laptop until it has been connected to the network?

[gizmo2005]

you might not be able to complete lock down but you could set the laptop so that it only connects to a certain IP address, they would have to bring them in to work on then unless you have external access set up for them, there must be sofware that locks the laptop after a certain amount of days, if you find one then please let me know

 

 

Giz

Edited August 26, 2010 by gizmo2005

[robmal]

1 - make it a condition of their user agreement

 

2 - justify it by explaining that if they don't log onto the school network regularly then the laptop won't have the up-to-date MS security patches, anti-virus signitures etc and they are expected as responsible users to comply

 

...... can't see what could possibly go wrong with that - lol!

[sted]

could you not add something to task scheduler that disabled their account (or just changed permissions of something) so login failed?

[Gatt]

@sted - this is what I am thinking:

 

A Scheduled task to check for the existence of $share (eg \\server\netlogon)

 

If $share has not been contacted within 14 days, do something that forces $user to connect the laptop to the network.

 

I was wondering if Reduced Functionality Mode could be manually activated, but I cant find anything on it..

 

Any other ideas would be appreciated....

[SYNACK]

Had a look at the KMS option. dosent look to be an option unfortunatly which is a total oversight on their part Activation Policy Values a script is probably the best way to go.

[Gatt]

Had a look at the KMS option. dosent look to be an option unfortunatly which is a total oversight on their part Activation Policy Values a script is probably the best way to go.

 

What a shame, because that could make a nice security feature, if the "KMS Activation Duration" values were configurable..

i doubt you could even script the KMS client to deactivate the PC by deleting the licensed state without rearming it...

[FN-GM]

I used to use a little script. When you logon connected to the domain in creates a small .txt file. There is another script that runs locally on logon and if the .txt is over 14 days it shuts down the computer.

[Gatt]

I used to use a little script. When you logon connected to the domain in creates a small .txt file. There is another script that runs locally on logon and if the .txt is over 14 days it shuts down the computer.

 

Sounds interesting - don't suppose you still have it? Does it work with non-domain machines?

[FN-GM]

The 2 schools that i used it with closed not long ago

 

I will see if i can find it.

[SYNACK]

What a shame, because that could make a nice security feature, if the "KMS Activation Duration" values were configurable..

i doubt you could even script the KMS client to deactivate the PC by deleting the licensed state without rearming it...

 

You could delete the KMS client key which would drop the activation state on the next reboot, not sure if you could drop it then re-add it in one hit and still have it drop the state. If not you could have it readd the key as part of the logon script if there was no key detected.

 

Slmgr.vbs Options

slmgr.vbs -upk {KMS Client Key}

 

there are some useful WMI headers to get the activation information out to check too:

Windows Product Activation Provider (Windows)

Win32_WindowsProductActivation Class (Windows)

 

The WMI stuff can also be used to add or remove keys

[srochford]

Why do you want them back in so frequently? I don't know how many you've got but getting them in every 2 weeks seems like an awful lot of work you're making for yourself?

[Gatt]

You could delete the KMS client key which would drop the activation state on the next reboot, not sure if you could drop it then re-add it in one hit and still have it drop the state. If not you could have it readd the key as part of the logon script if there was no key detected.

 

Slmgr.vbs Options

slmgr.vbs -upk {KMS Client Key}

 

there are some useful WMI headers to get the activation information out to check too:

Windows Product Activation Provider (Windows)

Win32_WindowsProductActivation Class (Windows)

 

The WMI stuff can also be used to add or remove keys

 

Cheers for that, I'll take a look into that

 

Why do you want them back in so frequently? I don't know how many you've got but getting them in every 2 weeks seems like an awful lot of work you're making for yourself?

 

We have 50 laptops going to the staff, I was for every month, but HT wanted every 2 weeks, it may be time to point out that it will (a) take up a lot of my time, and (b) annoy the hell out of the staff