Re: Local login on SBS 2003 needed from remote location.. How?

Obviously the apps simply aren't compatible with today's computing
environment, where the constant vigilance for security reasons is an
unfortunate reality. I know you say you're stuck with the apps, but being 16
bit apps the day may soon come when they're not even an option anymore.
Suddenly. If steps aren't taken to retire and replace them, 'stuck' will
extend to mean a business process that doesn't. A stuck business.

I feel for you, but I'd think twice about running these apps on the SBS -
another box perhaps.

Regarding updates and reboots, these are best done by a qualified and
competent administrator - rather than a local user with 'rights'. I see that
as a separate issue. RDP is your friend here.

--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !


"RobertNC" <RobertNC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:19C6C56D-25EC-4840-940B-13DF35C544F2@xxxxxxxxxxxxxxxx
> Yep. These apps can not be set to run as a service, and they even require
> PowerUser rights or better on the account that logs in. Talk about poor
> programming... But, I'm stuck with them and need to determine how to
> accomodate them. When installling Critical Updates that require server
> reboots, (or anything else for that matter), I'm trying to get away from
> giving local user(s) a UN & PW to log in locally that has what amounts to
> admin rights to the domain. It looks like purchasing PCAnywhere is the
> only
> way to do this, but I can't believe that Microsoft doesn't have the
> ability
> to control the environment as well or better than another company. I'm not
> sure at what level PCAnywhere connects to the server, and then initiates
> the
> log in locally, but it works for one client, and I have 2 others in the
> same
> situation. I don't want to force them to spend the $$ on PCAnywhere if I
> can
> avoid it.
> Logging in via RDP doesn't cut it, as the apps recognize it differently
> than
> the local login. Maybe the programmers own stock in Symantec...
> --
> Bob
>
>
> "Les Connor [SBS Community Member - SBS M" wrote:
>
>> BTW, yes you can logon to a server desktop with RDP and then 'disconnect'
>> from it, leaving the apps running. But this isn't what I'd consider best
>> practice; in fact it's a fairly poor practice.
>>
>> --
>> Les Connor [SBS Community Member - SBS MVP]
>> -----------------------------------------------------------
>> SBS Rocks !
>>
>>
>> "RobertNC" <RobertNC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:E320E98C-0C44-406D-8ED1-729EB6D21694@xxxxxxxxxxxxxxxx
>> > To clarify, I know I can remotely login, but what I want to do is
>> > initiate
>> > a
>> > session that would be recognized as a local login, not the normal
>> > remote
>> > sessions that are created through the methods you've outlined below.
>> > Due
>> > to
>> > 16 bit applications that require local login, my goal would be to leave
>> > a
>> > local session active with the desktop locked after disconnecting from
>> > the
>> > remote session. PCAnywhere allows this function, but I have not been
>> > able
>> > to
>> > mirror this with Microsoft technology. I've also seen this technology
>> > via
>> > McAfee Remote 32 to the pre XP desktops, (via Send Ctrl+Alt+Del
>> > function).
>> > Is
>> > this possible with any Microsoft technology?
>> > --
>> > Bob
>> >
>> >
>> > "Les Connor [SBS Community Member - SBS M" wrote:
>> >
>> >> For administrative purposes, yes you can log on to the SBS remotely
>> >> using
>> >> several methods.
>> >>
>> >> a) from the lan, use RDP (Remote Desktop Connection).
>> >> b) from the internet - RDP (needs port 3389 open)
>> >> c) from the internet - Remote Web Workplace, using administrator
>> >> level
>> >> credentials - and then 'connect to server computers' link.
>> >> d) from the internet VPN and then method a).
>> >>
>> >> There are 3 connections permitted in administrative mode - console
>> >> (session
>> >> 0), and sessions 1 and 2. I'd recommend the console session
>> >> exclusively
>> >> for
>> >> administrative purposes.
>> >>
>> >> --
>> >> Les Connor [SBS Community Member - SBS MVP]
>> >> -----------------------------------------------------------
>> >> SBS Rocks !
>> >>
>> >>
>> >> "RobertNC" <RobertNC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >> news:BFF797D6-233A-47D7-A749-EB82FF627DCB@xxxxxxxxxxxxxxxx
>> >> >I have the need to be able to initiate a local log in session on SBS
>> >> >2003
>> >> > from a remote location. PCAnywhere can do this, but can any
>> >> > Microsoft
>> >> > technology do this that is already included with SBS 2003?
>> >> > --
>> >> > Bob
>> >>
>> >>
>> >>
>>
>>
>>


.

Relevant Pages

  • file association
    ... I'm stuck with a silly thing: ... Box is redhat 9.0 ... If I right click on a file, I get a list of apps which could handle ... PS: Sorry for the dumb question:) ...
    (alt.os.linux.redhat)
  • Panel Bar-Auto Hide-Getting Stuck-FC3
    ... I find that if I set the bars as auto hide, they often get stuck and ... overlap the bottom of apps, or top, where I now have 1 set to. ...
    (Fedora)
  • Re: Python GUI toolkit
    ... have stuck with it, but then i saw the qt4 screenshot and couple of ... tell me that i should stick to wx or go forward with qt4. ... also, is qt4 apps better looking in both win/linux than wx apps, coz the ... widget system for *nix and mobile phones. ...
    (comp.lang.python)
  • Re: GTK-2 question
    ... I am stuck on having to use one theme for everything? ... It is bad usability to have application skinning. ... How many Windows apps, or rather Microsoft ... Do you Yahoo!? ...
    (Fedora)
  • Re: Local login on SBS 2003 needed from remote location.. How?
    ... Logging in via RDP doesn't cut it, as the apps recognize it differently than ... >> session that would be recognized as a local login, ... >> local session active with the desktop locked after disconnecting from the ... >> remote session. ...
    (microsoft.public.windows.server.sbs)