Managing a pc without disrupting user log in

[the_one_that_cant]

Morning.

 

I have been thinking (dangerous on a Monday morning) and I am wondering if there is anyway you can remote onto a user's pc without actually taking over the session?

 

I would like to be able to make basic changes such as set power options, change screen saver settings and the like without interfering with their session.

 

Would it be a case of updating a registery entry, or gaining access via the folders or such? (ie \\pcname\c$\whateverchangemade or am I thinking the impossible?

 

If it was to happen, no doubt I would have to reboot the machine for the change to take place? This is what I am hoping to avoid.

 

Cheers

[3s-gtech]

If you enabled Remote Desktop on the PC, you should be able to have two concurrent sessions - one remote and one local. That would do it.

[vikpaw]

From your own computer management screen i.e. right click computer and choose manage, you can connect to a remote computer.

From registry editor you can connect / load a remote registry too.

Not sure if that gives you access to the things you want though.

You can also like you said, connect with the hidden $ share.

Some of the settings you want to make are on a user's profile so you'd have to be them to do it.

I think you are better off looking at using Group Policy to push these sorts of settings, or are you intending to make user specific customisations..?

[vikpaw]

If you enabled Remote Desktop on the PC, you should be able to have two concurrent sessions - one remote and one local. That would do it.

 

I don't think that's possible. Certainly not without lots of hacking. It used to work on one flavor of windows but i'm pretty sure it's not there now.

[cpjitservices]

or if you use VNC, just choose listening session instead of Interactive this way you'll only be able to see whats on the users screen = but you wouldn't actually be able to make any changes.

[3s-gtech]

Vikpaw - yeah it's possible on XP, depends what OS they're on.

[Hightower]

I was under the impression that remote desktop connection on anything other than a server OS (so Win7 or XP etc) would log the current user off (or take over the session) when connected to remotely. I thought client OS's could only ever have one session.

[3s-gtech]

May be just on the one PC I have at home then

 

Remote management through AD U&C it is then!

[mac_shinobi]

you could establish what registry settings would make the said changes and either

 

1. Use group policy to make these changes

2. Have a startup script that ran the regedit changes in silent mode

 

Regedit /s File_Name.reg

 

http://www.robvanderwoude.com/regedit.php

[K.C.Leblanc]

you could establish what registry settings would make the said changes and either

 

1. Use group policy to make these changes

2. Have a startup script that ran the regedit changes in silent mode

 

 

 

Batch files - Use REGEDIT to add, read or delete registry values

 

 

Regshot is super handy for this type of stuff.

 

regshot | Download regshot software for free at SourceForge.net

[plexer]

or if you use VNC, just choose listening session instead of Interactive this way you'll only be able to see whats on the users screen = but you wouldn't actually be able to make any changes.

 

Which sort of defeats the purpose if you read what the OP is actually trying to do.

 

ben

[Arthur]

I thought you had to hack termsrv.dll to enable concurrent remote desktop connections on Windows client OSs?

[Ignatius]

How about using psexec to bring up a remote command shell (psexec \\RemoteIP cmd) then do what you need to do from the command line?

[vikpaw]

Vikpaw - yeah it's possible on XP, depends what OS they're on.

I was under the impression that remote desktop connection on anything other than a server OS (so Win7 or XP etc) would log the current user off (or take over the session) when connected to remotely. I thought client OS's could only ever have one session.

I thought you had to hack termsrv.dll to enable concurrent remote desktop connections on Windows client OSs?

 

That's what prompted my initial comment. I remember trying to hack windows XP, as it only ever did multiple in Windows 2000. For the hack, there's a caveat if in AD environment, that needs registry hacked.

 

I presume similar is needed for windows 7 now, as we use switch user remotely, but it still locks the machine for the end user, until we log out.

 

How about using psexec to bring up a remote command shell (psexec \\RemoteIP cmd) then do what you need to do from the command line?

 

I like the PS Tools suite, this is a good idea. I've never run a remote command line, i thought that once run, it still tries to execute commands locally. I've only every racked up a list of psexec to run a list of commands remotely.

 

We used to use PSKill to stop kids playing games in IT lessons.

 

I think group policy seems the way to do things properly, and also it's easier to manage, else when you need to go and make more changes, you'll have to remote in to each machine again.

[teejay]

There is a way to have multiple remote desktops on Windows 7, but in doing so you breach the license for Windows 7 as it's licensed for a single user only.

[vikpaw]

I'm guessing all the hacks are breach of license.

 

The simple solution is not to come up with bright ideas on a Monday, drink coffee and hide in the corner.

[Ignatius]

I like the PS Tools suite, this is a good idea. I've never run a remote command line, i thought that once run, it still tries to execute commands locally. I've only every racked up a list of psexec to run a list of commands remotely.

I'm not sure what you mean. If you get a Domain Admin command shell on your PC (using runas ...) then psexec \\RemoteIP cmd, it will bring up a command shell as if you're sitting at the remote PC. Test it by running ipconfig /all and you'll get the details from the remote PC rather than the local PC at which you're working.

 

I use the technique fairly often. The most recent was when I had to log a second user (a temp who was here for only 5 days) from a Windows 7 PC, using quser.exe and logoff.exe

[vikpaw]

i can't remember exactly. i just know that it wasn't straight forward for some reason when we tried it back then, or we had something weird conditions that meant it didn't work. i ended up just doing psexec \\remoteIP ipconfig and i think that worked.

 

anyway the tools are the dogs Bs. at some point weren't they going to be paid for/licensed, after M$ took over from Mark Russ''&**%ich.

Edited March 15, 2011 by vikpaw
clarity