Reply to thread

Message

<blockquote data-quote="dvdfreak" data-source="post: 220342" data-attributes="member: 21313">I can't really figure out why you would want to use remote desktop when TV Scheduler is specifically designed to be used from a remote client <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />&nbsp; What can be easier than running the management console on any client machine you wish? <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" />Web Access requires a good IIS setup, so I guess that is its weak point since IIS is not &quot;easy stuff&quot;.&nbsp; First IIS needs to be set up correctly on your server, then you need to make sure it's also correctly set up for the .NET Framework (&quot;aspnet_regiis -i&quot; may be needed).&nbsp; And then the Ajax extensions need to be properly installed too.Once all that is in place, and you have preferably tested IIS to run fine without Web Access installed, then the setup should run just fine.Now, all that being said, I can see if I can figure out what it is that is making the console crash on remote desktop connections... Looks like it is graphics-related somehow, remote desktop connections use a funky driver I guess.</blockquote>

[QUOTE="dvdfreak, post: 220342, member: 21313"] I can't really figure out why you would want to use remote desktop when TV Scheduler is specifically designed to be used from a remote client :) What can be easier than running the management console on any client machine you wish? :D Web Access requires a good IIS setup, so I guess that is its weak point since IIS is not "easy stuff". First IIS needs to be set up correctly on your server, then you need to make sure it's also correctly set up for the .NET Framework ("aspnet_regiis -i" may be needed). And then the Ajax extensions need to be properly installed too. Once all that is in place, and you have preferably tested IIS to run fine without Web Access installed, then the setup should run just fine. Now, all that being said, I can see if I can figure out what it is that is making the console crash on remote desktop connections... Looks like it is graphics-related somehow, remote desktop connections use a funky driver I guess. [/QUOTE]

Verification