Welcome, Guest
Please Login or Register.    Lost Password?

explorer.exe usability issue
(1 viewing) (1) Guest
Go to bottomPage: 1
TOPIC: explorer.exe usability issue
#3049
explorer.exe usability issue 8 Years, 1 Month ago Karma: 0
Hi folks,

I'm running into a bit of a strange problem that maybe others may have run into.

GO-Global server is a win2k3 server, with IE7. The server is joined to a windows 2000 mode active directory domain run by a win2k PDC and BDC. The GO-Global server local server remote desktop access is the default, limited to local administrators. There is no remote desktop users group for the domain since it is a 2000 type domain.

As per the FAQ, for a win2k3 GO-Global server with IE7, I made a copy of the explorer.exe executable and changed the name to fileexplorer.exe while locally logged in at the console as the local administrator. I actually made two copies, one located in the WINDOWS folder (published as Desktop1), the other in the GO-Global program folder (published as Desktop2). I made no changes to the file permissions.

Using standard authentication only with no password caching. Also using the "Apply Group Policy" option.


So, under the following cases, I get the following effects.

1. GO-Global client logon using the local administrator account, both Desktop1 and Desktop2 react normally.

2. Go-Global client logon using domainuser1, which appears to be a generic normal domain user, which has never interactively logged on at the server console. Desktop1 throws an error popup window showing that fileexplorer.exe had an application error (oxc00000fd) which appears to be a stack overflow error. There is nothing in the Windows Event Log. There is no zombie process in Task Manager. Even running the GO-Global log at level 6 only shows 3 relevant lines

"Application disconnected"
"Failed to assess if launch request for "Desktop1", process handle 0x00000308, is pending (code3,WLE0)"
"Process #7868 (fileexplorer.exe) stopped in session "domainuser1 on MyServer"

Using Desktop2, the application appears to start but no window opens. The GO-Global log only shows the relevant entry "Application disconnected" after the application start line in the log. Watching the task manager on the server when the user tries Desktop2, fileexplorer.exe does show as a process briefly before disappearing

Other published applications like Acrobat and Word seem to work normally.

3. Because the domain doesn't have a Remote Desktop Users Group, a domain user normally can not use remote desktop on the GO-Global server. I had domainuser1 log on at the server console once, when no GO-Global sessions were active. Having the user again try accessing through the GO-Global client, I get the same error for Desktop1, but now Desktop2 does work correctly and shows an explorer window.

4. I had another user, domainuser2, which should have the same user rights, who has never locally logged on or used the GO-Global client, perform a local console logon using domainuser2. Then I had them use the GO-Global client to log on. Results are the same as case 3.

5. Using yet another domain user, domainuser3, who has never locally logged on or used the GO-Global client, I added them manually to the server local Remote Desktop Users group. I had them then access the server via remote desktop and log on as domainuser3. Next they used the GO-Global client to log on. Results are the same as case 3.

6. Using yet another domain user, domainuser4, who has never locally logged on or used the GO-Global client, I next removed domainuser3 and added the Domain Users group to the server local Remote Desktop Users group. I then had them try the GO-Global client. Results are the same as case 2.

7. Using yet another domain user, domainuser5, who has never locally logged on or used the GO-Global client, I had them then access the server via remote desktop and log on as domainuser5. Next they used the GO-Global client to log on. Results are the same as case 3.


Now, I had hoped that any random domain user could use the GO-Global client without special preparation, but based on these results, it appears I am forced to make a domain user log onto the GO-Global server directly via at least remote desktop once before explorer works right. For procedural reasons, users will not be in a position to perform a remote desktop logon when they finally would want to use GO-Global. I realize I should also test without group policy, but in actual use group policies will be necessary.

So, is there some simple trick to get around this? Something like a change in the domain policies, or a specific point I should check for in existing domain policies? I keep getting the impression that some part of the permissions involving the INTERACTIVE or REMOTE INTERACTIVE user group is causing this.
Ouroboros
Fresh Boarder
Posts: 14
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#3051
Re:explorer.exe usability issue 8 Years, 1 Month ago Karma: 6
Publishing the desktop or explorer.exe is not supported. There may be suggestions/options/reasons to do this but this is not a supported or recommended configuration.
Erikt
Administrator
Posts: 591
graph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#3054
Re:explorer.exe usability issue 8 Years, 1 Month ago Karma: 0
If using explorer is an unsupported configuration, why is it explicitly explained in the FAQ without a warning regarding it being an unsupported configuration? And yes, I am aware that is not a full desktop, just a simple file explorer.
Ouroboros
Fresh Boarder
Posts: 14
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
Go to topPage: 1
Moderators: troy, Andyl