NewsArchive
02-24-2015, 03:24 AM
We have a customer location that's having a problem that I've not seen
before.
Part of our application suite is a Clarion executable that when the
user navigates from their workstation to the server, it creates a
shortcut to our app (which is on the server) on their desktop.
We've never had a problem with this at all, and it's been this way for
years and years.
Now at this site, however, although our shortcut maker shows
"success", there are no icons placed on the desktops of any of the
workstations.
This is a secure government site, and we have problems just sending
any old app for testing, as it has to go through the proper channels.
So I want to make sure I cover all of the bases before sending them
anything.
I'm wondering if there's a GPO (Group Policy) that re-directs the
desktop, or perhaps some other setting that prevents the tried & true
calls to SHGetSpecialFolderPath from locating the actual desktop that
the user sees.
I don't know where to start with this diagnosis. Anyone know what (if
any) group policies would or could cause this?
If this is the cause, what should I do to detect the desktop that the
user is actually seeing on their screen?
Any ideas?
Thanks.
Jeff Slarve
www.jssoftware.com
www.twitter.com/jslarve
I'll search help files & Google for you.
before.
Part of our application suite is a Clarion executable that when the
user navigates from their workstation to the server, it creates a
shortcut to our app (which is on the server) on their desktop.
We've never had a problem with this at all, and it's been this way for
years and years.
Now at this site, however, although our shortcut maker shows
"success", there are no icons placed on the desktops of any of the
workstations.
This is a secure government site, and we have problems just sending
any old app for testing, as it has to go through the proper channels.
So I want to make sure I cover all of the bases before sending them
anything.
I'm wondering if there's a GPO (Group Policy) that re-directs the
desktop, or perhaps some other setting that prevents the tried & true
calls to SHGetSpecialFolderPath from locating the actual desktop that
the user sees.
I don't know where to start with this diagnosis. Anyone know what (if
any) group policies would or could cause this?
If this is the cause, what should I do to detect the desktop that the
user is actually seeing on their screen?
Any ideas?
Thanks.
Jeff Slarve
www.jssoftware.com
www.twitter.com/jslarve
I'll search help files & Google for you.