jona <(E-Mail Removed)> wrote:
> "Lanwench [MVP - Exchange]"
> <(E-Mail Removed) hoo.com> wrote in
> message news:(E-Mail Removed)...
>> jona <(E-Mail Removed)> wrote:
>>> Hi all,
>>>
>>> Where would I find the setting to switch ON the warning that
>>> (network) users are logged on when the machine in question is
>>> restarted.
>>>
>>> In particular, the machine in question (XPpro-sp2) is running as
>>> the server for my IQ package. Every now and then someone
>>> (or myself) forgets this little detail and reboots the machine
>>> (for whatever reason) during the course of business. The machine
>>> quite happily does so without even the slightest hint that others
>>> are in fact accessing IQ data from the sales counter.
>>>
>>> Thanks for any help
>>> jona
>>
>> There's nothing that will tell you "other users are accessing shared
>> data on this computer" - what you're talking about sounds like the
>> warning you get when someone else is logged in (to a Terminal
>> Services session, or using 'switch users' . The fact that there's
>> network file/printer access won't cause the system to warn you.
>
> Wow. One would think that XP, in all it's sophistication, would be
> able to provide a simple feature like that. I mean, if it can warn when
> other users are logged on (a feature which is comparitively rarely
> used), then why not when other network users are "logged on".
Well - technically speaking, they *aren't* logged on. They're accessing data
across the network, authenticated once by a local account.
>
>> I don't know that I'd try to resolve this via technological
>> means.... why not just put a big sticker on the PC that says "Do not
>> reboot this during business hours" -?
>
> For the same reason that even traffic signs are sometimes "overlooked"
And those who ignore them are often arrested, right?
>
>> Although that said, if it's actually acting as a server, don't leave
>> it out on the floor like this, for anyone to walk up to.
>
> Well, it's a simple matter of resources. The PC in question needs to
> perform other daily tasks too.
Do you have an actual server on the network at all?
> I suppose one work around would be to
> create a user called 'server', fire up QB therein, and then switch to
> a different user to perform those other daily tasks.
Yes, it sounds like that would work - and would probably be better anyway.
Ah, this is Quickbooks? Ugh. I hate their new multiuser setup.
>
> Thanks for your reply. At least now I can terminate my lost cause
> searches.
You're welcome; hope it helps.
|