Welcome, Guest. Please login or register.

Login with username, password and session length

 
Advanced search

671 Posts in 206 Topics- by 599 Members - Latest Member: NMTBeheer

February 10, 2012, 02:59:54 AM
RES Software User Group ForumProductsWorkspace ManagerAutostart Res
Pages: [1]
Print
Author Topic: Autostart Res  (Read 2103 times)
mornevr
Newbie
*
Posts: 4


« on: October 22, 2009, 10:30:42 PM »

Hi,

This is probably a stupid question, but can someone tell me how to configure Res to automatically start when a specific user logs in?

Thanks
Logged
Yuri
RES Software User Group Administrator
Administrator
Newbie
*****
Posts: 46



WWW
« Reply #1 on: October 23, 2009, 10:20:04 AM »

You could specify [pwfsmgr.exe] to start automatically when an RDP session is connected to the Terminal server, or just publish the executable. On a workstation you could replace the shell.
Logged
mornevr
Newbie
*
Posts: 4


« Reply #2 on: October 23, 2009, 11:25:29 AM »

That is not quite what I am looking for. I would like to lock down only certain users on a particular machine. Say user1 and user2 share the same workstation. If user1 logs in, he gets the default and normal XP desktop, but if user2 logs in, he needs to be locked down by powerfuse.

Thanks
Logged
Yuri
RES Software User Group Administrator
Administrator
Newbie
*****
Posts: 46



WWW
« Reply #3 on: October 24, 2009, 08:38:47 AM »

You can set the shell on user level.
Logged
mornevr
Newbie
*
Posts: 4


« Reply #4 on: October 27, 2009, 07:08:12 AM »

I am very new at Res and have had no training, so I am basically an idiot when it comes to this software. You are going to have to explain it a little more for me to understand. Please bare with me.
Logged
Yuri
RES Software User Group Administrator
Administrator
Newbie
*****
Posts: 46



WWW
« Reply #5 on: October 28, 2009, 11:33:25 AM »

There's an entry called [WinLogon] in [SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] that values to explorer.exe. Try changing that to [pwfsmgr.exe] or [pwrstart.exe] including the path to your PowerFuse installation.
Logged
mornevr
Newbie
*
Posts: 4


« Reply #6 on: October 28, 2009, 11:43:59 AM »

That will change it for anyone who logs into the computer and not just for that specific user?
Logged
Yuri
RES Software User Group Administrator
Administrator
Newbie
*****
Posts: 46



WWW
« Reply #7 on: October 28, 2009, 02:32:44 PM »

HOWTO: Change the shell

To start the RES PowerFuse or RES Subscriber as shell when users log on, an administrator needs to set or change a key on computer or user level in the Windows registry.

User Key: [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
System Key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
Value Name: Shell
Data Type: REG_SZ (String Value)
Value Data: Path to executable of new shell

The default paths for RES PowerFuse and RES Subscriber are:
C:\Program Files\RES PowerFuse\pwrstart.exe
C:\Program Files\RES Subscriber\subscriber.exe
Logged
WTFoX
Newbie
*
Posts: 18



« Reply #8 on: February 24, 2010, 12:28:38 AM »

With the latest version of RES PowerFuse, the 2010 release (RC2 available now) it's possible to set the shell at the properties of an Agent in the RES PowerFuse Management Console. You can choose between 'manual' (explorer.exe) or 'automatic' (pfwsmgr.exe). This actually replaces the free setshell.exe utility and is ofcourse much more friendly from an administrative purpose.

Another friendly method to set the shell, is by using a default RES Wisdom task (set windows shell). You can choose from four options: Windows Explorer, RES PowerFuse, RES Subscriber or Custom.

Both methods are actually using the registry keys earlier mentioned in this thread by Yuri.
« Last Edit: February 24, 2010, 12:30:27 AM by WTFoX » Logged

flintstone_ctx
Newbie
*
Posts: 1


« Reply #9 on: March 01, 2010, 11:33:35 PM »

Create a GPO and attach it to a user group, user deny/apply. In this policy set "custom user interface" under the user part system.
Logged
WTFoX
Newbie
*
Posts: 18



« Reply #10 on: March 06, 2010, 02:21:31 PM »

Create a GPO and attach it to a user group, user deny/apply. In this policy set "custom user interface" under the user part system.

This is also an option. From my point of view the thing with GPO's is how to make a quick exclusion?
Logged

Pages: [1]
Print
Jump to: