顯示包含「Windows 2008」標籤的文章。顯示所有文章
顯示包含「Windows 2008」標籤的文章。顯示所有文章

2013年6月27日星期四

How to enable Ping in Windows Server

GUI – Graphical User Interface
1. Open Control Panel, then select System and Security by clicking on that header
-
-
2. Select Windows Firewall
-
-
3. Advanced Settings
-
-
4. In ‘Windows Firewall with Advanced security’ click on ‘Inbound rules’
-
-
5. Scroll down to ‘File and Printer sharing (Echo request – ICMPv4-In)
-
-
6. Rightclick on the rule and select ‘Enable rule’
-
-
Make sure that it turns green
Done, close down the ‘Windows Firewall with Advanced Security’ windows and then the Control panel.
Verify functionality by pinging the servers own IP address from a command or PowerShell prompt.
Done!
Back to top

-
-
PowerShell
(This will enable the existing rule exactly as the instruction above does)
Import-Module NetSecuritySet-NetFirewallRule -DisplayName “File and Printer Sharing (Echo Request – ICMPv4-In)” -enabled True
 
EnablePing
(ABove enables the existing rule, below will create a new rule that allows ICMPv4/Ping and enable it)
Import-Module NetSecurityNew-NetFirewallRule -Name Allow_Ping -DisplayName “Allow Ping”  -Description “Packet Internet Groper ICMPv4″ -Protocol ICMPv4 -IcmpType 8 -Enabled True -Profile Any -Action Allow
 
EnablePing2
(For IPv6 Ping you obviously enable the v6 Inbound Rule…)

2013年6月25日星期二

Installing Remote Desktop Services

Open the Server Manager and right-click on roles, select Add Roles from the context menu
Click next on the Before You Being page to bring up a list of Roles that can be installed, select Remote Desktop Services and click next
On the Introduction To Remote Desktop Services page click next, this will bring you to the Role Services page, select the Remote Desktop Session Host as well as the Remote Desktop Licensing Service and then click next.
When you get to the application compatibility page it tells you that you should install the Session Host Role before you install your applications, just click next as we have not yet installed our applications. You are then asked if you want to require NLA, this will only allow Windows clients to connect to the Remote Desktop Session Host Server, in addition they must be running a Remote Desktop Client that support Network Level Authentication. I will go ahead and require NLA and then click next

Now you have to choose a licensing method, most of you guys wont have Remote Desktop Client Access Licenses, so you can leave your option at Configure Later this will give you unlimited access to the Remote Desktop Server for 4 Months (120 Days). However, if you do have licenses here is some information help you make your choice:
Licensing Modes
The licenses you purchased can be used either as Per User or Per Device. It is purely up to you, however if you already have a RDS Licensing Server you will have to choose the same option you chose when importing the licenses originally.
  • RDS Per User CAL –  This means that every user that connects to the RDS Server must have a license. The user is assigned the license rather than the devices that he/she connects to the server from. This mode is a good choice if your users want to connect from a lot of different computers or devices (iPad, Home PC, Laptop, Phone etc)
  • RDS Per Device CAL – If your users share a common workstation this is the mode for you, the license is given to the device rather than the users, this way many people can connect from a single device. However, if they try to connect from a different device they will not be able to since their user account doesn’t have a license.
I will leave mine at configure later and click next
Now you should specify who can connect to the Remote Desktop Server, I will just add my user account (Windows Geek), then click next
You are now given the option of making the RDS Server look and act more like Windows 7, this is to avoid users getting confused when they see the classic theme. I will enable the all the settings, it requires more bandwidth though, so take your network traffic into account before going click-happy and selecting everything. Once you have made your choice click next
Since we are running Server 2008 R2, we don’t need to specify a Discovery Scope so just click next again
Finally you can click on install.
Once installation is complete, reboot your server, when you log in the configuration will complete. That’s all there is to installing a Remote Desktop Server.

Activation

If you need to install your licenses you can do it through the RD Licensing Manager. You will need to activate the Server first though. I wont go through this, as it is self-explanatory.
Once you have installed you Licenses you will need to specify a license server for the RDS Session Host to use, to do this, open the RDS Session Host Configuration MMC
When the console opens double-click on the Remote Desktop license servers link.
Now you can specify your licensing mode and then hit the add button to specify a licensing server.
As I said before, you can skip this activation section and use Remote Desktop Services for 120 Days before you need to purchase a CAL. Once you have done this you will need to install your applications. However you cant just install them in any fashion you want, there is actually a special method for installing applications on a Remote Desktop Server.

2011年12月29日星期四

Autologon in Windows 7 & Windows Server 2008


To enable Autologon in Windows 7 & Windows Server 2008,
1. Click Start, search for “control userpasswords2″ and press enter.
autologon1
2. Select the user from the list and uncheck “User must enter a user name and password to enter this computer” and click Apply and OK.

2010年11月16日星期二

Offline Domain Join (Djoin.exe) Step-by-Step Guide

The following procedures show how to grant the user rights with Group Policy and how to delegate the correct permissions.
Granting user rights to join workstations to the domain

You can use the Group Policy Management Console (GPMC) to modify the domain policy or create a new policy that has settings that grant the user rights to add workstations to a domain.

Membership in Domain Admins, or equivalent, is the minimum required to grant user rights. Review details about using the appropriate accounts and group memberships at Local and Domain Default Groups (http://go.microsoft.com/fwlink/?LinkId=83477).
To grant rights to join workstations to a domain

1.

Click Start, click Administrative Tools, and then click Group Policy Management.
2.

Double-click the name of the forest, double-click Domains, double-click the name of the domain in which you want to join a computer, right-click Default Domain Policy, and then click Edit.
3.

In the console tree, double-click Computer Configuration, double-click Policies, double-click Windows Settings, double-click Security Settings, double-click Local Policies, and then double-click User Rights Assignment.
4.

In the details pane, double-click Add workstations to domain.
5.

Select the Define these policy settings check box, and then click Add User or Group.
6.

Type the name of the account that you want to grant the user rights to, and then click OK twice.

Delegating permissions to join workstations to the domain

You can use a tool such as Ldp.exe to delegate permissions to join workstations to a domain. As a best practice, you should delegate permissions to a group, and then add users to the group or remove them as needed.

Membership in Domain Admins, or equivalent, is the minimum required to delegate permissions. Review details about using the appropriate accounts and group memberships at Local and Domain Default Groups (http://go.microsoft.com/fwlink/?LinkId=83477).
To delegate permissions to join workstations to a domain

1.

Click Start, click Run, type ldp, and then click OK.
2.

Click Connection, click Connect, and in Server type the name of a domain controller. If you are logged on to a domain controller, you can type localhost. When you are done, click OK.
3.

Click Connection, and then click Bind. If you are logged on as a member of the Domain Admins group, click Bind as currently logged on user. If you are logged on as a different user, click Bind with credentials, and then type the name, password, and domain of an account that is a member of the Domain Admins group. Click OK.
4.

Click View, click Tree, select DC=, and then click OK.
5.

In the console tree, double-click DC=, right-click CN=Computers,DC=, click Advanced, click Security Descriptor, and then click OK.
6.

Click ACE, click Add ACE, type the name of the account that you want to be able to join workstations to the domain, select the Create child check box, and then select the Inherit check box. In Object type, select computer ? class (you might have to type computer to select computer ? class), click OK, and then click Update.

Offline domain join process and Djoin.exe syntax

Run Djoin.exe at an elevated command prompt to provision the computer account metadata. When you run the provisioning command, the computer account metadata is created in a .txt file that you specify as part of the command. After you run the provisioning command, you can either run Djoin.exe again to request the computer account metadata and insert it into the Windows directory of the destination computer or you can save the computer account metadata in an Unattend.xml file and then specify the Unattend.xml file during an unattended operating system installation of the destination computer.

For more information about the NetProvisionComputerAccount function that is used to provision the computer account during an offline domain join, see NetProvisionComputerAccount Function (http://go.microsoft.com/fwlink/?LinkId=162426). For more information about the NetRequestOfflineDomainJoin function that runs locally on the destination computer, see NetRequestOfflineDomainJoin Function (http://go.microsoft.com/fwlink/?LinkId=162427).