[#CIB-1366] Support Windows 2000 guest clients

Pulse

Support Windows 2000 guest clients

Created: 24/Jan/08 07:14 AM Updated: 11/Dec/08 05:48 AM

Component/s:

Setup/Install, Build core

Affects Version/s:

1.2.32

Fix Version/s:

x.x

Environment:

Windows 2000 logged in as guest

Description

« Hide

One new restriction we have with our software is that it must work under Windows 2000 limited accounts logged in as guest.
We've found so far that many of our unit tests failed under this environment making it very important to run pulse with it.

When I start up pulse agent using it's batch file it just shuts down. This is without a doubt a file security issue.
Most applications including Visual Studio 2005 doesn't work under this condition ... so it's not surprising.

What are the chances of getting this as a supported environment?

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Daniel Ostermeier - 28/Jan/08 05:40 AM

Hi Henrik,

It all depends on the extent of the restrictions. We will need to investigate what the actual restrictions are, and then if we can work around them.

To be honest, this is unlikely to be part of 1.2.x, and probably not part of 2.0.x either.

But this all depends on what the actual restrictions are.

[ Permlink | « Hide ]

Daniel Ostermeier - 28/Jan/08 05:41 AM

Assigning to 1.2.x to investigate the limited account restrictions and then determine the appropriate scheduling.

[ Permlink | « Hide ]

Henrik Goldman - 28/Jan/08 07:04 AM

What I've tried for now is to start a agent as a service running as guest.
This didn't work out though which I didn't imagine it would either.

However as a normal user it just tries to startup and then shuts down immediately.

My experience working within this environment is that most applications doesn't work though.
What I observed is that settings are not preserved. E.g. things like backgrounds and icons are all reset on next login.

Also the only usable data path is the per-user data path:

SHGetFolderPath(NULL, CSIDL_APPDATA, NULL, 0, szPath)

Anything else is either working unreliably (system API failes when resolving the path) or the path is readonly.

I believe that if you only stick to the safe data paths then everything works out.

[ Permlink | « Hide ]

Daniel Ostermeier - 31/Jan/08 03:45 AM

Hi Henrik,

I have run some tests under windows XP (not 2000) and have had no troubles.

Before I can further investigate this, I will need to source a 2000 installation. Because I do not have one handy, I am going to have to push this into 2.0.x.

Cheers,
-Daniel

[ Permlink | « Hide ]

Henrik Goldman - 31/Jan/08 06:20 AM

Thats good progress.

I would assume they would be similar... but due to previous experiences it's not always the case.
In any case it's unlikely there are many problems if you tried it with XP guest accounts.

[ Permlink | « Hide ]

Daniel Ostermeier - 11/Dec/08 05:48 AM

Trying to clean things up a little. We currently have a couple of very large buckets of tasks that are really not indications of our scheduling. What I am doing is for starters, moving all of the 2.x. items into x.x to indicate that they have not been scheduled. We can later go through these and pick up with ones that we intend to complete for an upcoming release.