Al Dunbar [MS-MVP]" wrote:
: "Mark" wrote:
: > Roland
: > Whilst very helpful and you have just added another string to my bow I
: > like the users to have a yes/no
: > button option so that if they agree they get in and if they select no
: > get logged out.
: I think the phrase is "arrow to my quiver" rather than "string to my bow",
: but I digress.
: IMHO, if you have naughty people, you should consider having them sign a
: formal agreement that they understand and acknowledge the various written
: conditions of use policies. If someone does get logged in, then breaks
: rules and you take him to court, how could you prove that "he must have
: clicked on 'I agree', or he would not have gotten in". Even with a
: demonstration (questionable as that might be) a clever defence attorney
: ask you to prove that the mechanism was in place on the day in question,
: that it was completely foolproof.
: A related issue could be that those that want to abuse the company's
: technology are not likely the ones that take that technology seriously.
: Aside from that, it has been my experience that, whatever extra clicks or
: keystrokes needed to get into the system or an application becomes as
: automatic as hitting the enter key. Have you ever installed software and
: clicked the "I agree" button without actually reading the entire EULA?
: But if you want to do it:
: select case msgbox("EULA statement", vbYesNo or vbExclamation, "User
: Agreement" )
: case vbno
: call refuse()
: end select
: ' continue on with logon script
: The refuse function would either do a logout, shutdown, or restart of some
: If you were running logon scripts synchronously, I am not sure if the user
: could get to the task manager to simple terminate the script.
I agree with Al here, hence I stated 'one of...'. However, you also need it
on the computer, because hacker's have not signed your P&P agreement. It
also reinforces the rules in case of visitors. HR generally doesn't get
involved when a contractor comes in for an hour, day, etc., although forms
should be made available. Your P&P should always document when any all
modifications are made. These addendums should be sent out to everyone,
requiring a signature and data signed and added to their personnel file.
If you require acceptance prior to logging onto the workstation, their only
alternative is to not log on if they do not accept.
This line will keep you out of trouble: "By continuing to logon and use this
computer, you accept this agreement in full and agree to be bound by its
The law doesn't say they have to read it. It only says that it has to be
made available. If your logon script doesn't run for any reason, then it
wasn't made available. And, if your P&P procedure is not 100%, and you have
a high turnover rate, like we did (Offshore Drilling), people will come on
board sometimes who have not completed all of their HR documents. The
larger the organization, the more latency involved.
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Technet Script Center - http://www.microsoft.com/technet/scriptcenter/
WSH 5.6 Documentation - http://msdn.microsoft.com/downloads/list/we