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.

Windows 2008 Server Core R2 - Server roles available in different editions

30.May.2011 | by Gusac | Filed in: Articles, Tutorials

The server core installation of Microsoft Windows Server 2009 R2 provides minimal environment of running server roles. There are different editions of Server core available and the difference is the number of server roles available with them. The different editions available are: Web, Standard, Enterprise and Datacenter. The suitable edition of Windows 2008 Server Core R2 can be grabbed depending upon the  requirements. Here is the comparison chart: Server Roles Web Standard Enterprise DataCenter Active Directory Certificate Services No Yes Yes Yes Active Directory Domain Services No Yes Yes Yes Active Directory Lightweight Directory Services No Yes Yes Yes BranchCache Hosted Cache No No Yes Yes DHCP Server No Yes Yes Yes DNS Server Yes Yes Yes Yes File Services Yes Standalone DFS Yes Yes Hyper-V No Yes Yes Yes Media Services Yes Yes Yes Yes Print Services No Yes Yes Yes IIS Yes Yes Yes Yes

How to Disable SMB 2.0

26.Apr.2011 | by Gusac | Filed in: Articles

Windows Vista/2008 server and later OS have version 2 of SMB (Server Message Block), which also has backward compatibility with SMB 1.0. Even though, SMB 2.0 is tested to be faster, it might cause some issues in some scenarios and you may wan to disable it. There are different ways to disable SMB 2.0 at client end and server end. Disable SMB 2.0 at server end: Open Registry Editor (regedit.exe) and navigate to the following registry key": HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters Create a new DWORD value and rename it to: Smb2 Set the value data to 0. (0 denotes ‘Disable’) Restart the system Disable SMB 2.0 at client end: Open the command prompt (cmd.exe) and type the following two commands: sc config lanmanworkstation depend= bowser/mrxsmb10/nsi sc config mrxsmb20 start= disabled .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: consolas, "Courier New", courier, monospace; background-color: #ffffff; /*white-space: pre;*/ } .csharpcode pre { margin: 0em; } .csharpcode .rem { color: #008000; } .csharpcode .kwrd { color: #0000ff; } .csharpcode .str { color: #006080; } .csharpcode .op { color: #0000c0; } .csharpcode .preproc { color: #cc6633; } .csharpcode .asp { background-color: #ffff00; } .csharpcode .html { color: #800000; } .csharpcode .attr { color: #ff0000; } .csharpcode .alt { background-color: #f4f4f4; width: 100%; margin: 0em; } .csharpcode .lnum { color: #606060; } Please note, there is a space after the equal to (‘=’) sign in the command.

How file and folder permissions are handled while moving or copying files on Windows 2008 R2 and Windows 7

8.Apr.2011 | by Gusac | Filed in: Articles, Tutorials

There is just some logic with which Windows handles the file level permissions while moving or copying files from one location to another. Depending on the destination, be it the parent folder, same volume or a different one, the Access control Entries (ACE) are added or replaced from the file Access Control List (ACL) The way Windows 7 or Windows 2008 R2 handles the permissions while move/copy operation is different from previous version of Windows. This article talks only about how Windows 7 and Windows 2008 R2 server handles The table below has the source and destination folder with the type of operation performed. The result is provided against each operation Source Destination Operation Result         Child Folder Parent Folder Copy Both explicit and implicit Permissions are NOT retained. Permissions of destination parent folder are inherited. Chid Folder Parent Folder Move Explicit permissions are retained only and destination folder permissions are inherited. Same Volume       Same Volume, Folder A Same Volume, Folder B Copy Both explicit and implicit Permissions are NOT retained. Permissions of destination parent folder are inherited. Same Volume, Folder A Same Volume, Folder B Move All implicit and explicit permissions are retained. Destination parent folder permissions are NOT inherited. Different Volume       Folder A Folder B Copy Both explicit and implicit Permissions are NOT retained. Permissions of destination parent folder are inherited. Folder A Folder B Move Both explicit and implicit Permissions are NOT retained. Permissions of destination parent folder are inherited.

How to configure disk space threshold limit for event notification

2.Mar.2011 | by Gusac | Filed in: Articles, Tutorials

Configure the minimum percentage below of free disk space which Windows generates an event id to notify user [More]

Manage user accounts with NET USER command

16.Feb.2011 | by Gusac | Filed in: Articles, Tutorials

How to create, delete, modify user account using net use command line tool [More]