Monday, 25 April 2016

Windows Server 2012 and 2008 R2 – Enable Multiple RDP sessions

Problem:

Server 2012/2008 R2 unlike their predecessors, comes with the multiple remote desktop session restriction enabled. If you are only connecting to a server for remote administration purposes that can get a bit annoying, especially if you have a generic administrative account that multiple techs are using, and you keep kicking each other off the server.
Just as with earlier versions of Windows server you CAN have two RDP sessions at any one time, the restriction is one logon for one account. Thankfully you can disable the restriction and there are a number of ways to do so.

Solution:

Server 2008 R2 Option 1: Enable Multiple RDP sessions from TSCONFIG
Note: tsconfig.msc does not work on Windows Server 2012
1. On the server, click Start and in the search/run box type tsconfig.msc{enter}. Locate "Restrict each user to a single session" Right click > Properties.
TSCONFIG
2. Remove the tick from "Restrict each user to a single session" > Apply > OK.
Restric each logon to a single session

Server 2012 and 2008 R2 Option 2: Enable Multiple RDP sessions via the registry

1. Start > in the search/run box type regedit {enter} > Navigate to:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal Server
Locate the fSingleSessionPerUser value > Set it to 0 (Multiple sessions allowed), or 1 (Multiple sessions NOTallowed).
multiple rdp

Server 2012 and 2008 R2 Option 3: Enable Multiple RDP sessions via Local Policy

1. Start > in the search/run box type gpedit.msc {enter}.
GPO multiple RDP
2. Navigate to:
Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections
Locate the "Restrict Remote Desktop Services users to a single Remote Desktop Services session" setting.
Remote Desktop multiple logons group policy
3. To enable multiple sessions set the policy to disabled > Apply > OK.
RDP GPO

Server 2012 and 2008 R2 Option 4: Enable Multiple RDP sessions via Group Policy

1. On a domain controller > Start > in the search/run box type gpmc.msc {enter}.
local policy RDP
2. Either edit an existing GPO that's linked to your COMPUTERS, or create a new one and give it a sensible name.
group policy multiple logons
3. Navigate to:
Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections
Locate the "Restrict Remote Desktop Services users to a single Remote Desktop Services session" setting.
GPO 3389
4. To enable multiple sessions set the policy to disabled > Apply > OK.
more than one login
5. Then either reboot the clients, wait a couple of hours, or manually run "gpupdate /force" on them.
Force GPO

OR

Configure the Number of Simultaneous Remote Connections Allowed for a Connection

Applies To: Windows Server 2008 R2
You can configure the number of simultaneous remote connections that are allowed for a connection. Restricting the number of simultaneous remote connections can improve performance of the computer because fewer sessions are demanding system resources.
If the RD Session Host role service is not installed on the computer, a connection can only allow a maximum of two simultaneous remote connections to the computer.
Use the following procedure to configure the number of simultaneous remote connections allowed for a connection.
Membership in the local Administrators group, or equivalent, on the RD Session Host server that you plan to configure, is the minimum required to complete this procedure. Review details about using the appropriate accounts and group memberships athttp://go.microsoft.com/fwlink/?LinkId=83477.
To configure the number of simultaneous remote connections allowed for a connection
  1. On the RD Session Host server, open Remote Desktop Session Host Configuration. To open Remote Desktop Session Host Configuration, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Session Host Configuration.
  2. Under Connections, right-click the name of the connection, and then click Properties.
  3. In the Properties dialog box for the connection, on the Network Adapter tab, click Maximum connections, enter the number of simultaneous remote connections that you want to allow for the connection, and then click OK.
    If the Maximum connections option is selected and dimmed, the Limit number of connections Group Policy setting has been enabled and has been applied to the RD Session Host server.
You can also set the maximum number of simultaneous connections allowed for an RD Session Host server by applying the Limit number of connections Group Policy setting. This Group Policy setting is located in Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections and can be configured by using either the Local Group Policy Editor or the Group Policy Management Console (GPMC). Note that the Group Policy setting will take precedence over the setting configured in Remote Desktop Session Host Configuration.

Monday, 25 May 2015

On selecting the required company in Tally.ERP 9, the error message - Linkmgr.900 / Manager.900 file damage is dispalyed. How to overcome this?



On receiving such an error message, it is advised to take a backup of the data and follow the steps shown:
  • Include files with extension .900 and .tsf in the exclusion list of real time antivirus protection, incase the above error message appears for Tally.ERP 9 multi user edition.
  • Go to Gateway of Tally F12: Configuration > Data Configuration and set Load Companies on Startup to No
  • Rewrite the data by pressing Ctrl+Alt+R
  • Delete the following TSF files available in data folder of the respective company TSTATE.TSF, TUPDATE.TSF, TSTATE.TSF, TEXCEL.TSF, TACCESS.TSF
  • If required perform the Zero rewrite procedure
In case the problem persists restore the earlier backup.

We had changed the current period to 1-4-2009 to 31-3-2010 but it continues to display 1-4-2008 to 31-3-2009 as the current period in Gateway of Tally. What should I do?



It is essential to change the period to the next financial year before recording the transactions. On recording a transaction for the period 1/4/2009 – 31/3/2010, Tally.ERP 9 will automatically change the period to current financial year beginning from 1/4/2009 to 31/3/2010. On loading the company next time Tally.ERP 9 will display the current financial year.
You can also shut the company and select the same company again. While selecting the company, the financial years of the company are displayed in the List of Companies
In case multiple companies are loaded and the previous company contains a different financial year, it is suggested to follow the steps shown below and disable the load companies on startup.
 
  • Go to Gateway of Tally > F12: Configure > Data Configuration.
  • In the Data Configuration screen and set Load Companies on Startup to Yes
  • In the Companies to preload on startup select the required company from the List of Companies displayed.

While opening a company in Tally.ERP 9 we are getting error message Error in TDL Parts: Basic Company Insufficient Height to allocate! How can I resolve this?



You can check the screen resolution which should be set to 1024/768 and DPI setting should be set to Normal Size [96 DPI].
In case the screen resolution settings are other than the above you can change the resolution by following the steps shown:
For Windows 98 or Higher Operating Systems
  • Right click on Desktop
  • Select Properties
  • The Display Properties window appears
  • Click Settings tab
  • Drag and set the resolution to 1024 x 768 pixels
  • Click Advanced
  • Click General tab
  • From the DPI setting drop down list box select Normal Size (96 DPI)
  • Click Apply
  • Click OK
 
For Windows Vista Operating System:
  • Right click on the Desktop
  • Select Personalize 
  • Click Adjust Font Size (DPI)
  • Select Default scale (96 DPI)
  • Click Apply
  • Click OK.