Windows 2003 Terminal Server workgroup workaround
Hi All,
I would like to setup a 2003 server for 5 users. I run into a problem during setup. There is a program called Tidestone Formula One that I need to install on the server for the users so they will be able to open ".vts" files.
The serveris just a workgroup yet.
I have registered the TTF16.ocx (that is what tidestone F1 book needs) using "regsvr32" in the administrator profile. A have logged off and logged in as user.
The problem is that the user still cannot see that I have registered TTF16.ocx and receiving error message. After I gave the user administrator rights the error dissappear and tidestone F1 book ".vts" file opens up.
So the problem comes from the user rights, but don't know where should I start with.
Can you please help me?
Thanks
I would like to setup a 2003 server for 5 users. I run into a problem during setup. There is a program called Tidestone Formula One that I need to install on the server for the users so they will be able to open ".vts" files.
The serveris just a workgroup yet.
I have registered the TTF16.ocx (that is what tidestone F1 book needs) using "regsvr32" in the administrator profile. A have logged off and logged in as user.
The problem is that the user still cannot see that I have registered TTF16.ocx and receiving error message. After I gave the user administrator rights the error dissappear and tidestone F1 book ".vts" file opens up.
So the problem comes from the user rights, but don't know where should I start with.
Can you please help me?
Thanks
McKnife
You should start by checking if the terminal server has anything to do with this error, so install it on xp/vista/win7 ad see if it works with standard user rights. If not, ask the people of tidestone why they are not able to write software compatible to weak user accounts and demand a patch or solution. Even if this would not help, that's the first step. Please report back.
ASKER
Ok, so the problem comes from some kind of missing or invalid rights settings.
Was that a statement or a question?
If question, I cannot answer that. It might be badly programmed and, if so, there might be a solution (patch/update) for the program. That's why I tell you to contact the manufacturer.
If question, I cannot answer that. It might be badly programmed and, if so, there might be a solution (patch/update) for the program. That's why I tell you to contact the manufacturer.
ASKER
Yes, too bad that the manufacturer doesn't exist anymore. But however I could solve the problem using Active Directory insted of Workgroup policy.
Thanks anyway.
Thanks anyway.
It would be nice for others if you shared your solution. Until now I have no idea what about AD did solve it.
ASKER
yes, Active Directory was successfully solved the problem with its group policy.
Thanks for helping y'all.
Bye
Thanks for helping y'all.
Bye
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.