Cannot run Dragon as domain user Options

[Louis]

I'm deploying Dragon Naturally Speaking v7.3 in a 2003 domain but users are not allowed to launch dragon. The error message is about user has not enough read/write privilege in the program folder.

I found 3 ways to fix this:
1. Manually change folder permission as local administrator (this is too troublesome especially when I have to run about 200+ computer to do this)
2. User must be added into power user group (security breach)

Isn't there anything the developer can do to fix this? An application that can only be run as administrator will potentially cause huge security issue.

[John Wickett]

Louis,

You can push out DNS using Novell Application Launcher. Ditto, new commands. I have found it better to allow them power user rights as it permits tham to take care of their own machine.Most regular users don't even have the rights to runa defrag, which should be done often when using DNS.

Network techies can be much too anal. Are you not there to try and assist the user. I have seen networks where the user cannot login by voice to get to DNS but is expected to type user id and password when it could much easier be dictated. Saving the user the embarassement of asking soneone elseto log them in, even more of a security issue!

John

[Louis]

Thanks for the quick reply John. However, I couldn't understand the stuff you wrote in the second half of your reply

>>Are you not there to try and assist the user

I'm always there for the users and I'm quite shocked to find that DNS couldn't run with user privilege. So far, DNS is the second application after Winamp (older version) that has this flaw.

>>I have seen networks where the user cannot login by voice to get to DNS but is expected to type user id and password when it could much easier be dictated

I've worked with Windows domain for a long time and the concept is always the same. User logs in by typing username and password, then their profile gets loaded and DNS would then "supposedly" work. How can you dictate to login?

>>Saving the user the embarassement of asking soneone elseto log them in, even more of a security issue!

The users understand that DNS is the problem here. They still login as normal user and are not embarassed to call the network admins to type in the administrator password for them to run DNS whenever they need it.

Btw I'll check out the Novell Application Launcher, thanks for the feedback.

[John Wickett]

Louis,

>>I've worked with Windows domain for a long time and the concept is always the same. User logs in by typing username and password, then their profile gets loaded and DNS would then "supposedly" work. How can you dictate to login?

This has been a perennial problem. You could have DNS boot up before the profile login window comes up. That way they could dictate name and password using a macro to send keystrokes, I login with a macro called LAN Name and then use LANPass, no one ever hears me dictate the actual user name and password.

>>The users understand that DNS is the problem here
The problem is that they haven't been assigned sufficient rights! Just create a user group callled Dragon, put the users into the group and give them the rights to use Dragon. In some situations, you set the BIOS on the machine so that it cannt be turned off. There fore DNS is running when they get to their machine.

John

[Louis]

Ok, thanks for the reply