If you try to install Windows Defender by downloading a separate file as you would on XP, you will receive an error preventing you from installing.
Windows Server 2008 no need to download a separate file in order to install Windows Defender. To install Windows Defender on Server 2008 you first need to install the Desktop Experience which includes Windows Defender. Desktop Experience is available as a Feature from the Server Manager.
Following steps will show how to
Open the Server Manager, from the Features Summary click on Add Features.
From the Add Features Wizard select Desktop Experience and click one Next.
After Installing Desktop Experience feature we need to restart the Server
As the server will get restarted we will able to see following screen and Windows defender is operational
Scenario : While configuring the automated asset inventory I required a batch file to be executed during logon for every user in domain without any user intervention which will create a scheduled task in that system. So I landed up in configuring a group policy to execute the specified batch file.
So I have followed the following steps
- Open Active directory users and computer Snap-in
- Right on OU / Domain select properties
- Open The group policy tab
- Go in User configuration
- Select Administrative Tools – -> System – -> Logon – -> Run These Programs at User logons
- Double click Run These Programs at User logons
- Select Enabled radio button and click show button
- Now click on Add button and specify the network path of executable file
After the above steps I was able to execute the batch file on logon for user , but our motive to avoid user intervention was not getting fulfilled. Following is the screen shot which was coming on every desktop
The above screen was coming because default windows restricts the execution of external program which are getting deployed from group policy To get rid of it I followed the following steps
- Group Policy snap–in
- User configuration – -> Administrative Tools – -> Windows Component – -> Attachment Manager
- Double click on Inclusion list for low file types
- Click on Enabled radio button
- Type the extension name which you want to execute in our case it is .bat
After all the above steps the execution of batch file on logon for every user was without any user intervention… J
You may have a question that why I have not went for User profile à login script in User properties??? The issue for going such option is every time when we create new user we need to configure the login script manually for each user / new user. Moreover if we apply the above solution on OU or Domain level we need to worry for new users logins.
We regularly used to receive the call from developers that they are not able to take remote of local servers and the message they used to receive is the maximum number of connections error message as below
The terminal server has exceeded the maximum number of allowed connections
Traditionally we used to take the remote of that server with console or admin option and logoff the disconnected login
WE can do the same task remotely from our system (with admin rights) as below
- open the command prompt and type in the following command.
e.g. qwinsta /server:knowitvssserver
In the above sceenshot we can clearly see an Active RDP session with the ID 2 which belongs to the user Admin. In order to disconnect that user we are going to use the session ID.
2) Use the following command line to release the remote session.
Reset session <id> /server:Servername / IP
e.g. reset session 2 /server:knowitvssserver
We can confirm if the user is really disconnected. Just type in the qwinsta command in proper format as above