From: Jeff Pitsch on 14 Jul 2008 08:24 So the server is not in Appmode already? You are not using full blow terminal services then, you're using the remote admin mode. Remote admin mode is not licensed for use by end users but only administrators. You also want to make sure that before you switch over to appmode you know what you're doing. Putting a server into AppMode is not something you do on a whim. Special considerations on applications from installing to running must be taken into consideration. Jeff Pitsch Microsoft MVP - Terminal Services <stjoe5373(a)news.postalias> wrote in message news:%23nHVyoa5IHA.4776(a)TK2MSFTNGP05.phx.gbl... > Thanks All for the respones, Morgan when I try to change the compatibility > mode I receive > the message To change permission compatibility settings you must switch to > application server > mode in TS. How do I change to application mode? > Thanks again, Craig > > > "Morgan che(MSFT)" <v-morche(a)online.microsoft.com> wrote in message > news:CABOM2Y5IHA.1620(a)TK2MSFTNGHUB02.phx.gbl... >> Hi, >> >> As far as I know, some legacy applications were not designed for terminal >> server so they are incompatible with terminal server. They may require >> special access to system resources, such as the registry and system >> directories, in order to work correctly. As a result, you may notice that >> only administrators can run the application properly. Based on my >> experience, many permission issues are caused by registry and file access >> settings. We can try our best to check whether we can run the application >> without Local Administrators rights; however, as we have little >> understanding on how the application is developed and which permissions >> it >> needs, we are not the best resource for this issue. To troubleshoot this >> problem efficiently, I suggest that you contact the support engineer or >> developer of the application to see whether this software is compatible >> with terminal server and what permissions it needs to run. They are best >> resource for this issue. I appreciate your understanding. >> >> Having said that, I am still glad to provide some suggestions for your >> reference. In Windows 2003 terminal server, there are two Permission >> Compatibility modes: Full Security and Relaxed Security. Considering the >> current situation, let us perform the following steps to set the >> Permission >> Compatibility mode to Relaxed Security to see whether those applications >> work: >> >> 1. Open the Terminal Services Configuration snap-in, high light the >> Server >> Settings item. >> 2. Double click the "Permission Compatibility" item, and set it to >> "Relaxed >> Security" option, and click OK. >> 3. Restart the terminal server to test this issue again. >> >> The above option just opens the security permissions to the core registry >> keys and folders which are enough for most legacy applications; however, >> some applications may still have some special permission requirement on >> some folders and registry keys. If this problem continues, you can use >> the >> Regmon and Filemon tools to track the registry and file access >> information >> to see whether you receive "Access Denied" error and take corresponding >> action. >> >> 1. perform the following steps to use the FileMon tool to monitor the >> file >> access when you double click an Word document: >> >> - Logon to the console of the terminal server as administrator. Click the >> link below to download the tool named Filemon. >> http://www.microsoft.com/technet/sysinternals/utilities/filemon.mspx >> - Extract all the files from the ZIP file. >> - Double click the Filemon.exe to run the tool. >> - Click Clear icon on the toolbar. >> - Try to reproduce the problem by launching the application as a normal >> user. >> - When the error message is popped up, please click the File menu and >> uncheck "Capture Events". >> - Click the menu File-> Save, save the log to a .log file. >> >> 2. Please perform the following steps to use the RegMon tool to monitor >> the >> file access when you open an Office application >> >> - Please download the Registry Monitor (regmon) tool from >> http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/Regmon.msp >> x >> - Extract it and double click the regmon.exe to execute it. >> - From the Options menu, select Filter/Highlight, click the Defaults >> button >> and click OK. >> - Click the Edit menu and click Clear Display. >> - Try to reproduce the problem by launching the application as a normal >> user. >> - When the error message is popped up, please click the File menu and >> uncheck "Capture Events". >> - Click the menu File-> Save, save the log to a .log file. >> >> I hope that the above information can be of assistance. >> >> Sincerely >> Morgan Che >> Microsoft Online Support >> Microsoft Global Technical Support Center >> >> Get Secure! - www.microsoft.com/security >> ===================================================== >> When responding to posts, please "Reply to Group" via your newsreader so >> that others may learn and benefit from your issue. >> ===================================================== >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> >> -------------------- >> --->From: <stjoe5373(a)news.postalias> >> --->Subject: Permissions >> --->Date: Fri, 11 Jul 2008 08:17:30 -0400 >> --->Lines: 10 >> --->X-Priority: 3 >> --->X-MSMail-Priority: Normal >> --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138 >> --->X-RFC2646: Format=Flowed; Original >> --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 >> --->Message-ID: <#1YQYA14IHA.2064(a)TK2MSFTNGP02.phx.gbl> >> --->Newsgroups: microsoft.public.windows.terminal_services >> --->NNTP-Posting-Host: cblmdm72-240-127-118.buckeyecom.net 72.240.127.118 >> --->Path: >> TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl >> --->Xref: TK2MSFTNGHUB02.phx.gbl >> microsoft.public.windows.terminal_services:19041 >> --->X-Tomcat-NG: microsoft.public.windows.terminal_services >> ---> >> --->Hi, >> --->I'm using TS on a 2003 Server and I've got a user logging on and what >> not. >> --->I've installed a program with the >> --->Admin account and I can install and run it just fine but when I try >> to >> run >> --->the program under the other user account >> --->I'm getting a permission error. I can't seem to find where I change >> the >> --->permissions for a TS user so I can run the program. >> --->Thanks Craig >> ---> >> ---> >> ---> >> > >
From: stjoe5373 on 14 Jul 2008 08:35 Thanks Jeff, I screwed up any way it's SBS 2003, need I say more:) Craig "Jeff Pitsch" <jeff(a)jeffpitschconsulting.com> wrote in message news:e9kJhya5IHA.300(a)TK2MSFTNGP05.phx.gbl... > So the server is not in Appmode already? You are not using full blow > terminal services then, you're using the remote admin mode. Remote admin > mode is not licensed for use by end users but only administrators. You > also want to make sure that before you switch over to appmode you know > what you're doing. Putting a server into AppMode is not something you do > on a whim. Special considerations on applications from installing to > running must be taken into consideration. > > Jeff Pitsch > Microsoft MVP - Terminal Services > > > <stjoe5373(a)news.postalias> wrote in message > news:%23nHVyoa5IHA.4776(a)TK2MSFTNGP05.phx.gbl... >> Thanks All for the respones, Morgan when I try to change the >> compatibility mode I receive >> the message To change permission compatibility settings you must switch >> to application server >> mode in TS. How do I change to application mode? >> Thanks again, Craig >> >> >> "Morgan che(MSFT)" <v-morche(a)online.microsoft.com> wrote in message >> news:CABOM2Y5IHA.1620(a)TK2MSFTNGHUB02.phx.gbl... >>> Hi, >>> >>> As far as I know, some legacy applications were not designed for >>> terminal >>> server so they are incompatible with terminal server. They may require >>> special access to system resources, such as the registry and system >>> directories, in order to work correctly. As a result, you may notice >>> that >>> only administrators can run the application properly. Based on my >>> experience, many permission issues are caused by registry and file >>> access >>> settings. We can try our best to check whether we can run the >>> application >>> without Local Administrators rights; however, as we have little >>> understanding on how the application is developed and which permissions >>> it >>> needs, we are not the best resource for this issue. To troubleshoot this >>> problem efficiently, I suggest that you contact the support engineer or >>> developer of the application to see whether this software is compatible >>> with terminal server and what permissions it needs to run. They are best >>> resource for this issue. I appreciate your understanding. >>> >>> Having said that, I am still glad to provide some suggestions for your >>> reference. In Windows 2003 terminal server, there are two Permission >>> Compatibility modes: Full Security and Relaxed Security. Considering the >>> current situation, let us perform the following steps to set the >>> Permission >>> Compatibility mode to Relaxed Security to see whether those applications >>> work: >>> >>> 1. Open the Terminal Services Configuration snap-in, high light the >>> Server >>> Settings item. >>> 2. Double click the "Permission Compatibility" item, and set it to >>> "Relaxed >>> Security" option, and click OK. >>> 3. Restart the terminal server to test this issue again. >>> >>> The above option just opens the security permissions to the core >>> registry >>> keys and folders which are enough for most legacy applications; however, >>> some applications may still have some special permission requirement on >>> some folders and registry keys. If this problem continues, you can use >>> the >>> Regmon and Filemon tools to track the registry and file access >>> information >>> to see whether you receive "Access Denied" error and take corresponding >>> action. >>> >>> 1. perform the following steps to use the FileMon tool to monitor the >>> file >>> access when you double click an Word document: >>> >>> - Logon to the console of the terminal server as administrator. Click >>> the >>> link below to download the tool named Filemon. >>> http://www.microsoft.com/technet/sysinternals/utilities/filemon.mspx >>> - Extract all the files from the ZIP file. >>> - Double click the Filemon.exe to run the tool. >>> - Click Clear icon on the toolbar. >>> - Try to reproduce the problem by launching the application as a normal >>> user. >>> - When the error message is popped up, please click the File menu and >>> uncheck "Capture Events". >>> - Click the menu File-> Save, save the log to a .log file. >>> >>> 2. Please perform the following steps to use the RegMon tool to monitor >>> the >>> file access when you open an Office application >>> >>> - Please download the Registry Monitor (regmon) tool from >>> http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/Regmon.msp >>> x >>> - Extract it and double click the regmon.exe to execute it. >>> - From the Options menu, select Filter/Highlight, click the Defaults >>> button >>> and click OK. >>> - Click the Edit menu and click Clear Display. >>> - Try to reproduce the problem by launching the application as a normal >>> user. >>> - When the error message is popped up, please click the File menu and >>> uncheck "Capture Events". >>> - Click the menu File-> Save, save the log to a .log file. >>> >>> I hope that the above information can be of assistance. >>> >>> Sincerely >>> Morgan Che >>> Microsoft Online Support >>> Microsoft Global Technical Support Center >>> >>> Get Secure! - www.microsoft.com/security >>> ===================================================== >>> When responding to posts, please "Reply to Group" via your newsreader so >>> that others may learn and benefit from your issue. >>> ===================================================== >>> This posting is provided "AS IS" with no warranties, and confers no >>> rights. >>> >>> >>> -------------------- >>> --->From: <stjoe5373(a)news.postalias> >>> --->Subject: Permissions >>> --->Date: Fri, 11 Jul 2008 08:17:30 -0400 >>> --->Lines: 10 >>> --->X-Priority: 3 >>> --->X-MSMail-Priority: Normal >>> --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138 >>> --->X-RFC2646: Format=Flowed; Original >>> --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 >>> --->Message-ID: <#1YQYA14IHA.2064(a)TK2MSFTNGP02.phx.gbl> >>> --->Newsgroups: microsoft.public.windows.terminal_services >>> --->NNTP-Posting-Host: cblmdm72-240-127-118.buckeyecom.net >>> 72.240.127.118 >>> --->Path: >>> TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl >>> --->Xref: TK2MSFTNGHUB02.phx.gbl >>> microsoft.public.windows.terminal_services:19041 >>> --->X-Tomcat-NG: microsoft.public.windows.terminal_services >>> ---> >>> --->Hi, >>> --->I'm using TS on a 2003 Server and I've got a user logging on and >>> what >>> not. >>> --->I've installed a program with the >>> --->Admin account and I can install and run it just fine but when I try >>> to >>> run >>> --->the program under the other user account >>> --->I'm getting a permission error. I can't seem to find where I change >>> the >>> --->permissions for a TS user so I can run the program. >>> --->Thanks Craig >>> ---> >>> ---> >>> ---> >>> >> >> > >
From: Jeff Pitsch on 14 Jul 2008 08:50 LOL, no more needs to be said. :) It happens to the best of us. Jeff Pitsch Microsoft MVP - Terminal Services <stjoe5373(a)news.postalias> wrote in message news:%23Nvvf4a5IHA.4560(a)TK2MSFTNGP04.phx.gbl... > Thanks Jeff, > I screwed up any way it's SBS 2003, need I say more:) > Craig > "Jeff Pitsch" <jeff(a)jeffpitschconsulting.com> wrote in message > news:e9kJhya5IHA.300(a)TK2MSFTNGP05.phx.gbl... >> So the server is not in Appmode already? You are not using full blow >> terminal services then, you're using the remote admin mode. Remote admin >> mode is not licensed for use by end users but only administrators. You >> also want to make sure that before you switch over to appmode you know >> what you're doing. Putting a server into AppMode is not something you do >> on a whim. Special considerations on applications from installing to >> running must be taken into consideration. >> >> Jeff Pitsch >> Microsoft MVP - Terminal Services >> >> >> <stjoe5373(a)news.postalias> wrote in message >> news:%23nHVyoa5IHA.4776(a)TK2MSFTNGP05.phx.gbl... >>> Thanks All for the respones, Morgan when I try to change the >>> compatibility mode I receive >>> the message To change permission compatibility settings you must switch >>> to application server >>> mode in TS. How do I change to application mode? >>> Thanks again, Craig >>> >>> >>> "Morgan che(MSFT)" <v-morche(a)online.microsoft.com> wrote in message >>> news:CABOM2Y5IHA.1620(a)TK2MSFTNGHUB02.phx.gbl... >>>> Hi, >>>> >>>> As far as I know, some legacy applications were not designed for >>>> terminal >>>> server so they are incompatible with terminal server. They may require >>>> special access to system resources, such as the registry and system >>>> directories, in order to work correctly. As a result, you may notice >>>> that >>>> only administrators can run the application properly. Based on my >>>> experience, many permission issues are caused by registry and file >>>> access >>>> settings. We can try our best to check whether we can run the >>>> application >>>> without Local Administrators rights; however, as we have little >>>> understanding on how the application is developed and which permissions >>>> it >>>> needs, we are not the best resource for this issue. To troubleshoot >>>> this >>>> problem efficiently, I suggest that you contact the support engineer or >>>> developer of the application to see whether this software is compatible >>>> with terminal server and what permissions it needs to run. They are >>>> best >>>> resource for this issue. I appreciate your understanding. >>>> >>>> Having said that, I am still glad to provide some suggestions for your >>>> reference. In Windows 2003 terminal server, there are two Permission >>>> Compatibility modes: Full Security and Relaxed Security. Considering >>>> the >>>> current situation, let us perform the following steps to set the >>>> Permission >>>> Compatibility mode to Relaxed Security to see whether those >>>> applications >>>> work: >>>> >>>> 1. Open the Terminal Services Configuration snap-in, high light the >>>> Server >>>> Settings item. >>>> 2. Double click the "Permission Compatibility" item, and set it to >>>> "Relaxed >>>> Security" option, and click OK. >>>> 3. Restart the terminal server to test this issue again. >>>> >>>> The above option just opens the security permissions to the core >>>> registry >>>> keys and folders which are enough for most legacy applications; >>>> however, >>>> some applications may still have some special permission requirement on >>>> some folders and registry keys. If this problem continues, you can use >>>> the >>>> Regmon and Filemon tools to track the registry and file access >>>> information >>>> to see whether you receive "Access Denied" error and take corresponding >>>> action. >>>> >>>> 1. perform the following steps to use the FileMon tool to monitor the >>>> file >>>> access when you double click an Word document: >>>> >>>> - Logon to the console of the terminal server as administrator. Click >>>> the >>>> link below to download the tool named Filemon. >>>> http://www.microsoft.com/technet/sysinternals/utilities/filemon.mspx >>>> - Extract all the files from the ZIP file. >>>> - Double click the Filemon.exe to run the tool. >>>> - Click Clear icon on the toolbar. >>>> - Try to reproduce the problem by launching the application as a normal >>>> user. >>>> - When the error message is popped up, please click the File menu and >>>> uncheck "Capture Events". >>>> - Click the menu File-> Save, save the log to a .log file. >>>> >>>> 2. Please perform the following steps to use the RegMon tool to monitor >>>> the >>>> file access when you open an Office application >>>> >>>> - Please download the Registry Monitor (regmon) tool from >>>> http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/Regmon.msp >>>> x >>>> - Extract it and double click the regmon.exe to execute it. >>>> - From the Options menu, select Filter/Highlight, click the Defaults >>>> button >>>> and click OK. >>>> - Click the Edit menu and click Clear Display. >>>> - Try to reproduce the problem by launching the application as a normal >>>> user. >>>> - When the error message is popped up, please click the File menu and >>>> uncheck "Capture Events". >>>> - Click the menu File-> Save, save the log to a .log file. >>>> >>>> I hope that the above information can be of assistance. >>>> >>>> Sincerely >>>> Morgan Che >>>> Microsoft Online Support >>>> Microsoft Global Technical Support Center >>>> >>>> Get Secure! - www.microsoft.com/security >>>> ===================================================== >>>> When responding to posts, please "Reply to Group" via your newsreader >>>> so >>>> that others may learn and benefit from your issue. >>>> ===================================================== >>>> This posting is provided "AS IS" with no warranties, and confers no >>>> rights. >>>> >>>> >>>> -------------------- >>>> --->From: <stjoe5373(a)news.postalias> >>>> --->Subject: Permissions >>>> --->Date: Fri, 11 Jul 2008 08:17:30 -0400 >>>> --->Lines: 10 >>>> --->X-Priority: 3 >>>> --->X-MSMail-Priority: Normal >>>> --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138 >>>> --->X-RFC2646: Format=Flowed; Original >>>> --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 >>>> --->Message-ID: <#1YQYA14IHA.2064(a)TK2MSFTNGP02.phx.gbl> >>>> --->Newsgroups: microsoft.public.windows.terminal_services >>>> --->NNTP-Posting-Host: cblmdm72-240-127-118.buckeyecom.net >>>> 72.240.127.118 >>>> --->Path: >>>> TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl >>>> --->Xref: TK2MSFTNGHUB02.phx.gbl >>>> microsoft.public.windows.terminal_services:19041 >>>> --->X-Tomcat-NG: microsoft.public.windows.terminal_services >>>> ---> >>>> --->Hi, >>>> --->I'm using TS on a 2003 Server and I've got a user logging on and >>>> what >>>> not. >>>> --->I've installed a program with the >>>> --->Admin account and I can install and run it just fine but when I try >>>> to >>>> run >>>> --->the program under the other user account >>>> --->I'm getting a permission error. I can't seem to find where I change >>>> the >>>> --->permissions for a TS user so I can run the program. >>>> --->Thanks Craig >>>> ---> >>>> ---> >>>> ---> >>>> >>> >>> >> >> > >
From: v-morche on 21 Jul 2008 23:20 Hi, I am wirting to see how evertything is going? Have this issue been sovled or you need further assistance? please feel free to let me know. Sincerely Morgan Che Microsoft Online Support Microsoft Global Technical Support Center Get Secure! - www.microsoft.com/security ===================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- --->From: <stjoe5373(a)news.postalias> --->Subject: Permissions --->Date: Fri, 11 Jul 2008 08:17:30 -0400 --->Lines: 10 --->X-Priority: 3 --->X-MSMail-Priority: Normal --->X-Newsreader: Microsoft Outlook Express 6.00.2900.3138 --->X-RFC2646: Format=Flowed; Original --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 --->Message-ID: <#1YQYA14IHA.2064(a)TK2MSFTNGP02.phx.gbl> --->Newsgroups: microsoft.public.windows.terminal_services --->NNTP-Posting-Host: cblmdm72-240-127-118.buckeyecom.net 72.240.127.118 --->Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl --->Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.terminal_services:19041 --->X-Tomcat-NG: microsoft.public.windows.terminal_services ---> --->Hi, --->I'm using TS on a 2003 Server and I've got a user logging on and what not. --->I've installed a program with the --->Admin account and I can install and run it just fine but when I try to run --->the program under the other user account --->I'm getting a permission error. I can't seem to find where I change the --->permissions for a TS user so I can run the program. --->Thanks Craig ---> ---> --->
First
|
Prev
|
Pages: 1 2 Prev: Remote Application Center v3.0 Next: Windows Server 2008 Terminal Services in W2K AD Domain? |