Remote Desktop into locked workstations on the logged in session

[Guest StandardGreen]

My organization is on the cusp of implementing a policy that requires

all employees to lock their workstations when they're not at their

desks. That's all fine and dandy, except we in IT have grown

accustomed to receiving a help desk request and simply walking to the

user's station while they're away, sitting down, and doing whatever

task needs to be done. The other common scenario would be this: One of

us is walking by a cubicle, notices J. Random User isn't at his desk

which reminds us that he needed [n] done to his machine. Great! I'll

just sit down and do it while he's away. But when all users start

locking their stations, this option is no longer viable. Unless...

 

Is there a tool that can remotely log into an existing _locked_

session and interact with it? That would make our jobs more

streamlined and expedite the mandatory lock policy. We own Dameware v5

and v6, but as far as we know it cannot do this task.

 

Of course, we could bump people off their sessions but that just

wouldn't be nice.

 

Thanks in advance,

 

 

StandardGreem

[Guest Soo Kuan Teo [MSFT]]

Re: Remote Desktop into locked workstations on the logged in session

 

What is the Windows versions of workstations are you running?

Thanks

Soo Kuan

 

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

 

"StandardGreen" <StandardGreen@gmail.com> wrote in message

news:1191600266.637705.19300@w3g2000hsg.googlegroups.com...

> My organization is on the cusp of implementing a policy that requires

> all employees to lock their workstations when they're not at their

> desks. That's all fine and dandy, except we in IT have grown

> accustomed to receiving a help desk request and simply walking to the

> user's station while they're away, sitting down, and doing whatever

> task needs to be done. The other common scenario would be this: One of

> us is walking by a cubicle, notices J. Random User isn't at his desk

> which reminds us that he needed [n] done to his machine. Great! I'll

> just sit down and do it while he's away. But when all users start

> locking their stations, this option is no longer viable. Unless...

>

> Is there a tool that can remotely log into an existing _locked_

> session and interact with it? That would make our jobs more

> streamlined and expedite the mandatory lock policy. We own Dameware v5

> and v6, but as far as we know it cannot do this task.

>

> Of course, we could bump people off their sessions but that just

> wouldn't be nice.

>

> Thanks in advance,

>

>

> StandardGreem

>

[Guest StandardGreen]

Re: Remote Desktop into locked workstations on the logged in session

 

On Oct 5, 12:55 pm, "Soo Kuan Teo [MSFT]"

<sooku...@online.microsoft.com> wrote:

> What is the Windows versions of workstations are you running?

> Thanks

> Soo Kuan

>

> --

> This posting is provided "AS IS" with no warranties, and confers no rights.

>

> "StandardGreen" <StandardGr...@gmail.com> wrote in message

>

> news:1191600266.637705.19300@w3g2000hsg.googlegroups.com...

>

> > My organization is on the cusp of implementing a policy that requires

> > all employees to lock their workstations when they're not at their

> > desks. That's all fine and dandy, except we in IT have grown

> > accustomed to receiving a help desk request and simply walking to the

> > user's station while they're away, sitting down, and doing whatever

> > task needs to be done. The other common scenario would be this: One of

> > us is walking by a cubicle, notices J. Random User isn't at his desk

> > which reminds us that he needed [n] done to his machine. Great! I'll

> > just sit down and do it while he's away. But when all users start

> > locking their stations, this option is no longer viable. Unless...

>

> > Is there a tool that can remotely log into an existing _locked_

> > session and interact with it? That would make our jobs more

> > streamlined and expedite the mandatory lock policy. We own Dameware v5

> > and v6, but as far as we know it cannot do this task.

>

> > Of course, we could bump people off their sessions but that just

> > wouldn't be nice.

>

> > Thanks in advance,

>

> > StandardGreem

 

Ah, of course. How could I forget? Windows XP Professoinal (with a

smattering of 2000 Pro machines that are going to be phased out soon

[hopefully]. If the 2000 Pro machines muddle the situation, just

ignore them.)

 

Thanks,

 

S.G.

[Guest Leythos]

Re: Remote Desktop into locked workstations on the logged in session

 

In article <1191600266.637705.19300@w3g2000hsg.googlegroups.com>,

StandardGreen@gmail.com says...

> My organization is on the cusp of implementing a policy that requires

> all employees to lock their workstations when they're not at their

> desks. That's all fine and dandy, except we in IT have grown

> accustomed to receiving a help desk request and simply walking to the

> user's station while they're away, sitting down, and doing whatever

> task needs to be done. The other common scenario would be this: One of

> us is walking by a cubicle, notices J. Random User isn't at his desk

> which reminds us that he needed [n] done to his machine. Great! I'll

> just sit down and do it while he's away. But when all users start

> locking their stations, this option is no longer viable. Unless...

 

LOL, as a user you should not have rights to do anything significant on

their machines anyway - at least not IT tasks.

 

Locking when away is the standard in most medical, pharmacy, doctors,

government, military, anyplace that wants to protect data.

> Is there a tool that can remotely log into an existing _locked_

> session and interact with it? That would make our jobs more

> streamlined and expedite the mandatory lock policy. We own Dameware v5

> and v6, but as far as we know it cannot do this task.

>

> Of course, we could bump people off their sessions but that just

> wouldn't be nice.

 

We remotely support almost 3000 client nodes, not counting servers. It's

a simple matter to VNC to their PC and open notepad and ask them if we

can work on XYZ for them. You can also call their desk and tell them

it's time...

 

If they don't have time or their console is locked then they wait for

the next time we have time to fix it.

 

You can also install the HELP desk feature of Sharepoint and allow them

to enter items in the HD and you can keep track (and they can monitor)

progress on tasks.

 

If a user is not being fired you should not be in their session without

them being there.

 

Yea, doesn't answer your need, but it fixes your perception problem.

 

--

 

Leythos

- Igitur qui desiderat pacem, praeparet bellum.

- Calling an illegal alien an "undocumented worker" is like calling a

drug dealer an "unlicensed pharmacist"

spam999free@rrohio.com (remove 999 for proper email address)

[Guest StandardGreen]

Re: Remote Desktop into locked workstations on the logged in session

 

On Oct 5, 7:43 pm, Leythos <v...@nowhere.lan> wrote:

> In article <1191600266.637705.19...@w3g2000hsg.googlegroups.com>,

> StandardGr...@gmail.com says...

>

> > My organization is on the cusp of implementing a policy that requires

> > all employees to lock their workstations when they're not at their

> > desks. That's all fine and dandy, except we in IT have grown

> > accustomed to receiving a help desk request and simply walking to the

> > user's station while they're away, sitting down, and doing whatever

> > task needs to be done. The other common scenario would be this: One of

> > us is walking by a cubicle, notices J. Random User isn't at his desk

> > which reminds us that he needed [n] done to his machine. Great! I'll

> > just sit down and do it while he's away. But when all users start

> > locking their stations, this option is no longer viable. Unless...

>

> LOL, as a user you should not have rights to do anything significant on

> their machines anyway - at least not IT tasks.

 

o contraire mon amie: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/runas.mspx?mfr=true

 

> We remotely support almost 3000 client nodes, not counting servers. It's

> a simple matter to VNC to their PC and open notepad and ask them if we

> can work on XYZ for them. You can also call their desk and tell them

> it's time...

>

> If they don't have time or their console is locked then they wait for

> the next time we have time to fix it.

[snip]

> If a user is not being fired you should not be in their session without

> them being there.

 

We've already done the notepad trick a few times. It's nice to

initiate a remote session when they're on the phone with you. As to

not being on a user's session, I suppose its a matter of

organizational culture. In our environment of a little more than 200

users it's an accepted practice. I was a bit gun shy about it when I

first got there, but when I realized how accepted it was, I got over

it. We'd like to start leaving our desks to fix problems less often

which implies an increased reliance on remote tools. With this locking

policy in place (which IT is generally happy about) it will, however,

reduce our windows of opportunity... unless we can find a workaround.

 

But I can see from your viewpoint.

 

Still hopping for a workaround...

....StandardGreen

[Guest Soo Kuan Teo [MSFT]]

Re: Remote Desktop into locked workstations on the logged in session

 

Can you please share what are the typical tasks you need to perform on the

employee's physical console workstation?

I thinking some of the tasks may be possible to do them remotely.

 

Thanks

Soo Kuan

 

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

 

"StandardGreen" <StandardGreen@gmail.com> wrote in message

news:1191632396.432952.259320@19g2000hsx.googlegroups.com...

> On Oct 5, 7:43 pm, Leythos <v...@nowhere.lan> wrote:

>> In article <1191600266.637705.19...@w3g2000hsg.googlegroups.com>,

>> StandardGr...@gmail.com says...

>>

>> > My organization is on the cusp of implementing a policy that requires

>> > all employees to lock their workstations when they're not at their

>> > desks. That's all fine and dandy, except we in IT have grown

>> > accustomed to receiving a help desk request and simply walking to the

>> > user's station while they're away, sitting down, and doing whatever

>> > task needs to be done. The other common scenario would be this: One of

>> > us is walking by a cubicle, notices J. Random User isn't at his desk

>> > which reminds us that he needed [n] done to his machine. Great! I'll

>> > just sit down and do it while he's away. But when all users start

>> > locking their stations, this option is no longer viable. Unless...

>>

>> LOL, as a user you should not have rights to do anything significant on

>> their machines anyway - at least not IT tasks.

>

> o contraire mon amie:

> http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/runas.mspx?mfr=true

>

>

>> We remotely support almost 3000 client nodes, not counting servers. It's

>> a simple matter to VNC to their PC and open notepad and ask them if we

>> can work on XYZ for them. You can also call their desk and tell them

>> it's time...

>>

>> If they don't have time or their console is locked then they wait for

>> the next time we have time to fix it.

> [snip]

>> If a user is not being fired you should not be in their session without

>> them being there.

>

> We've already done the notepad trick a few times. It's nice to

> initiate a remote session when they're on the phone with you. As to

> not being on a user's session, I suppose its a matter of

> organizational culture. In our environment of a little more than 200

> users it's an accepted practice. I was a bit gun shy about it when I

> first got there, but when I realized how accepted it was, I got over

> it. We'd like to start leaving our desks to fix problems less often

> which implies an increased reliance on remote tools. With this locking

> policy in place (which IT is generally happy about) it will, however,

> reduce our windows of opportunity... unless we can find a workaround.

>

> But I can see from your viewpoint.

>

> Still hopping for a workaround...

> ...StandardGreen

>

>

>

>

[Guest StandardGreen]

Re: Remote Desktop into locked workstations on the logged in session

 

On Oct 8, 11:23 am, "Soo Kuan Teo [MSFT]"

<sooku...@online.microsoft.com> wrote:

> Can you please share what are the typical tasks you need to perform on the

> employee's physical console workstation?

> I thinking some of the tasks may be possible to do them remotely.

>

> Thanks

> Soo Kuan

>

> --

> This posting is provided "AS IS" with no warranties, and confers no rights.

>

> "StandardGreen" <StandardGr...@gmail.com> wrote in message

>

> news:1191632396.432952.259320@19g2000hsx.googlegroups.com...

>

>

>

> > On Oct 5, 7:43 pm, Leythos <v...@nowhere.lan> wrote:

> >> In article <1191600266.637705.19...@w3g2000hsg.googlegroups.com>,

> >> StandardGr...@gmail.com says...

>

> >> > My organization is on the cusp of implementing a policy that requires

> >> > all employees to lock their workstations when they're not at their

> >> > desks. That's all fine and dandy, except we in IT have grown

> >> > accustomed to receiving a help desk request and simply walking to the

> >> > user's station while they're away, sitting down, and doing whatever

> >> > task needs to be done. The other common scenario would be this: One of

> >> > us is walking by a cubicle, notices J. Random User isn't at his desk

> >> > which reminds us that he needed [n] done to his machine. Great! I'll

> >> > just sit down and do it while he's away. But when all users start

> >> > locking their stations, this option is no longer viable. Unless...

>

> >> LOL, as a user you should not have rights to do anything significant on

> >> their machines anyway - at least not IT tasks.

>

> > o contraire mon amie:

> >http://www.microsoft.com/resources/documentation/windows/xp/all/prodd...

>

> >> We remotely support almost 3000 client nodes, not counting servers. It's

> >> a simple matter to VNC to their PC and open notepad and ask them if we

> >> can work on XYZ for them. You can also call their desk and tell them

> >> it's time...

>

> >> If they don't have time or their console is locked then they wait for

> >> the next time we have time to fix it.

> > [snip]

> >> If a user is not being fired you should not be in their session without

> >> them being there.

>

> > We've already done the notepad trick a few times. It's nice to

> > initiate a remote session when they're on the phone with you. As to

> > not being on a user's session, I suppose its a matter of

> > organizational culture. In our environment of a little more than 200

> > users it's an accepted practice. I was a bit gun shy about it when I

> > first got there, but when I realized how accepted it was, I got over

> > it. We'd like to start leaving our desks to fix problems less often

> > which implies an increased reliance on remote tools. With this locking

> > policy in place (which IT is generally happy about) it will, however,

> > reduce our windows of opportunity... unless we can find a workaround.

>

> > But I can see from your viewpoint.

>

> > Still hopping for a workaround...

> > ...StandardGreen- Hide quoted text -

>

> - Show quoted text -

 

The tasks aren't predictable. They're more like... "I get this error

message when I open Outlook." or "My computer's slow." or "Can you

install this application?" etc. Most purely administrative tasks can

be done through the Computer Management MMC or command prompt. If we

were that desparate to do something remotely, PsExec might do the

trick.

 

However, the tasks that are most benefited by remote control ala

Dameware/VNC/Remote Desktop are the ones that require a bit of

sleuthing to fix and thusly need hands-on visualization. E.g. "I get

this error message when I open Outlook" would require a decent

googling of the error message at my workstation, but then probably

some configurating at the client machine that is best done hands on.

Great! Call the user or drop by their workstation... but they're not

there and the screen is locked. Do I waste time and play phone tag for

an afternoon and try and cram in the support follow-up when they show

up? I'd rather do what we've always done and what our users expect and

fix the problem while they're away. Same with the "My computers slow!"

Okay, when do you go to lunch 'cause it'll need 20 minutes do to the

Malware Triad (Spybot, Ad-Aware, Hijack This), plus any extra special

techniques that might be necissitated. Etc., etc.

 

I've spent some more time researching the subject but still no clues

on remoting into a locked workstation with an admin account on top of

the user's logged in session. ::scratches head::

 

The search continues...

 

 

StandardGreen