Custom Tool: trying to open remote system ntfs

[Trammel]

Hyena v8.1
Running on windows 7 with a custom tool for simply opening up file systems on select machine.

explorer "\\%E%\c$\Documents and Settings"
(works just fine)

This does not however work from a windows XP system. I have tried multiple commands trying to get this tool to work successful from Windows XP.

I have tried many variations but am unable to mimic that of a Windows 7 system.

[cmccullough]

Re: Custom Tool: trying to open remote system ntfs

So what happens when you try to run it on XP?

[Trammel]

Re: Custom Tool: trying to open remote system ntfs

Absolutely nothing, which is weird.

Tried
c:\windows\explorer.exe "\\%E%\c$\Documents and Settings"

cmd /c explorer "\\%E%\c$\Documents and Settings"

"\\%E%\c$\Documents and Settings"

\\%E%\c$

Something is just different how XP handles the commands versus Windows 7. Figured I would come here and see if anyone knew.

[cmccullough]

Re: Custom Tool: trying to open remote system ntfs

The first one works fine for me on an XP computer, so I'm not sure what you are running into.

[Trammel]

Re: Custom Tool: trying to open remote system ntfs

So I run Hyena with runas here in my environment. Worked some more today on this issue and discovered if I just launch Hyena with my one account, the custom tool (cmd) works.

explorer "\\%E%\c$\Documents and Settings"

The difference is that I am using a config.ini file on the two account. So some setting is preventing this command from running in that config file on a windows xp system.

[cmccullough]

Re: Custom Tool: trying to open remote system ntfs

I don't see how any settings would affect that, but you can easily test by simply removing the config from the account that doesn't work and see what happens.

[Trammel]

Re: Custom Tool: trying to open remote system ntfs

Strange Chuck

I removed the config.ini setting for the two account and even replaced all the DAT files. Still nothing. Deleted the two account profile from the machine. Still doesn't work.

SO, my thought is that when running on Windows XP. Those who use the option "Run as" and try this command, won't work.

Launch your Hyena with a Run as Chuck and then try to execute this custom tool.
explorer "\\%E%\c$\Documents and Settings"

[cmccullough]

Re: Custom Tool: trying to open remote system ntfs

I was able to duplicate it on an XP computer, but have no clue what is different with Run As under XP.

I'll check with Development to see if there are any theories.

[cmccullough]

Re: Custom Tool: trying to open remote system ntfs

Development gave me several options to test, but nothing works.

You will see this same issue if you open the Command Prompt and enter explorer. That works. Close the Command Prompt window, then right-click on it and choose Run As to run the Command Prompt. Type explorer again and you should see the same thing that happens when run from Hyena.

This was the theory from Development:

Some Windows versions of Explorer run in a different security context than the logged in user. The idea is that Explorer is part of the system itself and not really a separate application like notepad, etc. So when you 'run' it, in some cases you are only showing the application as its actually already running. There might even be a process sitting out there just waiting for the launch command. Probably helps performance too. In any case, since its already running, its running on the security context of the user who originally logged on.

[Trammel]

Re: Custom Tool: trying to open remote system ntfs

Very nice, why is it I seem to find those weird bugs?

Found a work around using this command:
<span style="font-weight: bold">"C:\Program Files\Internet Explorer\iexplore.exe" "\\%E%\c$"</span>
This is a bit slower but it does work.

Found this http://blogs.msdn.com/b/aaron_margos...07/175488.aspx on the web and by simply logging on my system with the account I use for runas. Go in to folder options and Check “Launch folder windows in a separate process.†Then log off and back on with my normal account. WALLA!

Now the original command works!

[This message has been edited by Trammel (edited 12-30-2010).]