The more you tell us the more we can help. Can you help us improve? Resolved my issue. Clear instructions. Easy to follow.
No jargon. Pictures helped. Didn't match my screen. Incorrect instructions. Too technical. In the past, you had to download the resource kit tools separately. For example, if you install the Active Directory Domain Services server role, all of the tools needed to support that role are installed on the server i. Some tools, such as kerbtray , have suitable replacements in the Windows Server and Windows Server R2 releases. Physical server to Virtual server migration: the same migration tools can be used to migrate physical servers to new bit virtual guest sessions running on Microsoft Hyper-V or VMware.
Active Directory and Active Directory to Active Directory R2: the migration tools include migration wizards, tools, and migration procedures for migrating to the latest version of Active Directory. Print Server Migration: tools and a step by step guide is provided to help with the migration of existing print servers running on Windows and Windows to bit Windows R2 print servers, including migrating printer definition files, configuring new drivers, configuring print settings, reapplying user and administrative permissions, etc.
Certificate of Authority Migration: this is a new one, I just reviewed it a couple weeks ago, helps you migrate your Certificate Server off a Windows or box, to a new Windows R2 box yet keep all of your certificates, policies, configurations, etc Includes a VB script that assists with the migraiton. The migration of leases is a huge thing. When other clients on the same network request this content, the client does a quick check to make sure its local, cached copy is equivalent to the live copy at the head office, and, if so, serves up that copy to its client colleague over the faster LAN.
Content can be web-based HTTP or typical files and folders SMB , can be configured to work over SSL or IPSec-encrypted connections, and all security is maintained through an authorization process controlled by the host servers, not the 'mini servers' holding the cache in the remote office. In a demo, a document was downloaded over a KB connection, taking about 30 to 45 seconds. After the cache, when another user in the same site requested that information, the transfer was nearly instantaneous.
BranchCache works not only with a branch office server but also on a peer-to-peer basis among Windows 7 clients in the same location. Next, check out the name you need to configure the client computers to look for by entering PowerShell and issuing the following commands:. Next, we have to allow the Windows Firewall on all involved computers to let BranchCache connections in. Finally, we have to work the other way and let Windows Firewall accept outbound BranchCache connections as well.
To check the status of the cache, use the following command at a command prompt to display the amount of data stored in the hosted cache: Netsh branchcache show status all. Some of the more interesting improvements present in the publicly available release candidate build of Windows Server include new support for administering Active Directory via PowerShell and a new GUI that replaces the ancient and decrepit administrative tool that's been with us for the last decade.
As development on Windows Server R2 continues, there are sure to be more features you'll be able to test in your own environment.
Stay tuned for more. Jonathan Hassell is an author, consultant and speaker on a variety of IT topics. His published works include a variety of books on Windows client and server, including Learning Windows Server He also speaks worldwide on topics ranging from networking and security to Windows administration.
0コメント