Widget Tag cloud not found.

Unable to cast object of type 'ASP.widgets_tag_cloud_widget_ascx' to type 'App_Code.Controls.WidgetBase'.X

Widget RecentPosts not found.

Unable to cast object of type 'ASP.widgets_recentposts_widget_ascx' to type 'App_Code.Controls.WidgetBase'.X

Widget Search not found.

Unable to cast object of type 'ASP.widgets_search_widget_ascx' to type 'App_Code.Controls.WidgetBase'.X

Widget Visitor info not found.

Unable to cast object of type 'ASP.widgets_visitor_info_widget_ascx' to type 'App_Code.Controls.WidgetBase'.X

How to enable Remote Desktop on Windows Server 2012

16.Jul.2012 | by Gusac | Filed in: Articles, Tutorials

In Windows 2012, the usual Remote Desktop window is not easily visible. To launch the Remote Desktop window, there are two methods: Command Line and Graphical User Interface. Command Line 1. Move your mouse to bottom right of the screen and you would see a bar, Charm Bar. 2. Click on the Search button, the one with magnifying glass. See the screenshot below: 3. Enter CMD in the Apps search text box: 4. Click on CMD on the left, it will launch the command prompt: 5. In command prompt window, type SystemPropertiesRemote and hit Enter 6. The above command would launch the System Properties windows. 7. Select the appropriate option under Remote Desktop and click OK.   Graphical Interface 1. Move your mouse to bottom right of the screen and you would see a bar, Charm Bar. 2. Click on the Settings button, 3. Click on Server Info under Desktop 4. The Server Info launches the Control Panel System page. Click Advance System Settings on the right. This would launch the same System Properties page. 5. Select the appropriate option under Remote Desktop and click OK.

Changes in mstsc /admin switch

17.May.2012 | by Gusac | Filed in: Articles, Troubleshoot, Tutorials

As most of you know by now that since Windows server 2008, mstsc.exe has replaced old /console switch with new /admin switch. This article talks about the behavior when you connect to an administrative session using the /admin switch. Below are the behavioral changes: It does not connect to session 0 of the server unlike /console switch. This is because the session 0 on Windows 2008 and later operating system is used exclusively for the system services. Client access license is not used. If you have Remote desktop services role installed with configured CALs, using this switch will not use one of the CALs. We can have only two sessions on the server including session using /admin switch. This different from previous version where we could have two remote desktop sessions and a third console session using /console switch. Time zone and Plug-n-Play device redirection is not available with /admin session Easy Print feature is not available in the session. Administrative sessions (/admin) are not counted towards session limit.

RemoteApp program does not save settings in roaming profile

11.Dec.2011 | by Gusac | Filed in: Articles, Troubleshoot

Issue: A RemoteApp application does not retain settings when users have roaming profile. To reproduce the issue: Start the application, make changes and exit out. Next time you start it, it will not retain the settings.   Solution: Remoteapp default setting is to disconnect the session whenever a user closes out the application by click on the X at top right corner. The best thing is to exit the Remoteapp program from its menu (Ex: File > Exit) Or, Group Policy can be  configured to change the default behaviour of Remoteapp. Enabled the following policy on your Windows 2008 Terminal Server: Computer configuration > Administrative templates > Windows component > Terminal Services > Terminal server > Session Time Limit = ‘Immediately’   Set the value to 'Immediately'   Explanation: This policy setting allows you to specify how long a user's RemoteApp session will remain in a disconnected state before the session is logged off from the terminal server. By default, if a user closes a RemoteApp program, the session is disconnected from the terminal server. If you enable this policy setting, when a user closes a RemoteApp program, the RemoteApp session will remain in a disconnected state until the time limit that you specify is reached. When the time limit specified is reached, the RemoteApp session will be logged off from the terminal server. If the user starts a RemoteApp program before the time limit is reached, the user will reconnect to the disconnected session on the terminal server. If you disable or do not configure this policy setting, when a user closes a RemoteApp program, the session will be disconnected from the terminal server.

Fallback Printer Driver

22.Sep.2011 | by Gusac | Filed in: Articles, Tutorials

Overview of Fallback printer driver policy and how it is configured [More]

Windows 2008 R2 RDWeb - Unable to connect via RD Gateway

10.Apr.2011 | by Gusac | Filed in: Articles, Troubleshoot

RD Gateway error while connecting via RD web connection [More]

Error: ‘RPC Server Unavailable’ while logging into RDP Session

26.Jan.2011 | by Gusac | Filed in: Articles, Troubleshoot

Issue: While connecting a server through remote desktop, you get the login screen but after entering the login credential you get the error message: ‘RPC Server Unavailable’ and it does not let you login. In Application logs, we get error with event id 1219, Source: Winlogon and the description of the event is: ‘Logon rejected for <user name>. Unable to obtain Terminal Server User Configuration.’ Things to check: Create the Following DWORD value and set it to 1 HKeyLocalMachine\SYSTEM\CurrentControlSet\Control\Terminal Server IgnoreRegUserConfigErrors =1 Roaming Profiles – Test with an account that has local profile. Reference: KB 821929 Network Binding Order Disable TCP Chimney and RSS on the network adapter. Reference KB 948496 Incorrect DNS server configuration on the server.

Microsoft utility: Remote Desktop Connection Manager - RDCMan

3.Jun.2010 | by Gusac | Filed in: Articles, Tools

Microsoft has recently release a new utility called Remote Desktop Connection Manager or RDCman. Its just like RDP Desktops or Remote desktop mmc snap-ins but with more features. It supports server list and groups and can save configurations setting to connect to Terminal servers.  As per Microsoft site: "RDCMan manages multiple remote desktop connections. It is useful for managing server labs where you need regular access to each machine such as automated checkin systems and data centers. It is similar to the built-in MMC Remote Desktops snap-in, but more flexible. " Few of the benefits: Different groups can be created to manage servers based on common configuration setting, geographical location etc. Global settings at Group level can be saved which are inheritable by servers in that group or servers can be configured individually. Gives you the option to connect with different screen resolutions, applicable both at group or server level. Main window shows the preview of all the connected servers. As per Microsoft Download page, RDCman is supported on Operating systems: Windows 7; Windows Server 2003; Windows Server 2008; Windows Server 2008 R2; Windows Vista Users using Windows XP or Windows Server 2003 will need to obtain version 6 or newer of the Remote Desktop Connection client software Click here to go to the download page