A
Aaron B.
Hey guys,
Just up front - This is not a show stopper problem for me. But, it does
cause a little eye rolling from other admins who I am trying to get to start
using this tool...
I created a little script that pops up when an administrator shutsdown a
server or logs out (gpedit.msc kicks it off) of a server that dumps what the
admin did on the server into a centeralized database. Then we all can see
what each other did on a box and everyone is familiar with the history of
what is going on.
The only wierd thing though is that one can't cut and paste from *the client
desktop* to the servers "activity log form" (aka the script that kicks off)
while the script is being used during the shutdown/logoff process. You CAN
cut and paste to and from the RDP window itself though...
Notes:
** You CAN cut and paste to the script if you call it up BEFORE
shutdown/logoff.
** It's almost as if some part of the RDP client clipboard mapping is turned
off before the gpedit.msc can execute the User Configuration -> Windows
Settings -> Scripts -> Logoff area of the GPEdit.msc
** You CAN cut and paste from inside the RDP session just fine
** You CAN NOT cut and paste from the client desktop to the RDP session.
Like I said this is not a show stopper, but it would be nice to be able to
cut and paste the same text to multiple server "activity logs" when we are
doing patches and stuff. Right now my work around is to use a unc admin path
to dump the file with activity log response and then open that file inside of
the RDP window during shutdown/logoff and paste the answer in. OR I will
just call it up before shutdown/logoff, but that defeats the purpose because
I want this activity log to be in the admins face. =)
Just up front - This is not a show stopper problem for me. But, it does
cause a little eye rolling from other admins who I am trying to get to start
using this tool...
I created a little script that pops up when an administrator shutsdown a
server or logs out (gpedit.msc kicks it off) of a server that dumps what the
admin did on the server into a centeralized database. Then we all can see
what each other did on a box and everyone is familiar with the history of
what is going on.
The only wierd thing though is that one can't cut and paste from *the client
desktop* to the servers "activity log form" (aka the script that kicks off)
while the script is being used during the shutdown/logoff process. You CAN
cut and paste to and from the RDP window itself though...
Notes:
** You CAN cut and paste to the script if you call it up BEFORE
shutdown/logoff.
** It's almost as if some part of the RDP client clipboard mapping is turned
off before the gpedit.msc can execute the User Configuration -> Windows
Settings -> Scripts -> Logoff area of the GPEdit.msc
** You CAN cut and paste from inside the RDP session just fine
** You CAN NOT cut and paste from the client desktop to the RDP session.
Like I said this is not a show stopper, but it would be nice to be able to
cut and paste the same text to multiple server "activity logs" when we are
doing patches and stuff. Right now my work around is to use a unc admin path
to dump the file with activity log response and then open that file inside of
the RDP window during shutdown/logoff and paste the answer in. OR I will
just call it up before shutdown/logoff, but that defeats the purpose because
I want this activity log to be in the admins face. =)
