Microsoft Windows Server 2008 R2 will be the next version of the Windows Server operating system from Microsoft. Building on the features and capabilities of the current Windows Server 2008 release version, Windows Server 2008 R2 allows you to create solutions organization that are easier to plan, deploy, and manage than previous versions of Windows Server.

 

 

Building upon the increased security, reliability, and performance provided by Windows Server 2008, Windows Server 2003 R2 extends connectivity and control to local and remote resources. This means your organizations can benefit from reduced costs and increased efficiencies gained through enhanced management and control over resources across the enterprise.

 

 

Here you can download the documents “Windows_Server_2008_R2_Reviewers_Guide_(BETA)” released from Microsoft...

From PDC 2008 arrive news on Windows Server 2008 r2, the next version of Microsoft server operating system. Let's See what are the interesting things that have been revealed:

 

 

Note: Windows Server 2008 R2 will be only 64Bit.

 

 

·         Virtualization:

 

 

 

 

• Live Migration

   

• Clustered Shared Volumes

   

• RemoteApp and Desktop Connection (RAD

   

• Terminal Services Broker

   

• Protocollo RDP

   

• Interoperabilità con Windows Azure

   

• Management:

   

• Un nuovo insieme di management console per la gestione dei diversi ruoli server

   

• PowerShell v. 2

   

• A new console for AD

   

• An extension of  Group Policy

   

•  

• Web: update of IIS7

   

  • Native management  via PowerShell

     

  • Extension will be available with IIS.NET

     

  • New reporting  options

     

  • Improved support for  Silverlight and PHP

     

 

 

• Direct Access

   

For more information pleases go to following links:

  Blog of team developer of Windows Server

 Official Site of Windows Server 2008 R2

 

Last week a Gartner chart comparing virtualization vendors market shares and their hypervisors’ features generated a lot of buzz as, for example, Oracle VM was reported as more used than Microsoft Hyper-V.

 

The chart was included in a recent article from Datamation, but Gartner said that it was part of November 2007 report.
The analysis firm has requested the news magazine to update its article with the newest version of that chart, based on projections made on March 2008. Let’s compare the two diagrams:

November 2007

March 2008

Read all from source Virtualization.info

LOS ANGELES — Oct. 27, 2008 — Today, during a keynote speech at the Microsoft Professional Developers Conference 2008 (PDC2008), Ray Ozzie, Microsoft Corp.’s chief software architect, announced Windows Azure, the cloud-based service foundation underlying its Azure Services Platform, and highlighted this platform’s role in delivering a software plus services approach to computing. The Azure Services Platform is an industry-leading move by Microsoft to help developers build the next generation of applications that will span from the cloud to the enterprise datacenter and deliver compelling new experiences across the PC, Web and phone.

 

Watch an on-demand Webcast of Microsoft chief technology officer Ray Ozzie's keynote speech at Microsoft's PDC below:

 

Watch in stand-alone player.

I wanted to call your attention to a critical, out-of-band Microsoft Security Bulletin released yesterday.

 

This security update resolves a privately reported vulnerability in the Server service. The vulnerability could allow remote code execution if an affected system received a specially crafted RPC request. On Microsoft Windows 2000, Windows XP, and Windows Server 2003 systems, an attacker could exploit this vulnerability without authentication to run arbitrary code. It is possible that this vulnerability could be used in the crafting of a wormable exploit. Firewall best practices and standard default firewall configurations can help protect network resources from attacks that originate outside the enterprise perimeter. This security update is rated Critical for all supported editions of Microsoft Windows 2000, Windows XP, Windows Server 2003, and rated Important for all supported editions of Windows Vista and Windows Server 2008. For more information, see the subsection, Affected and Non-Affected Software, in this section.

 

Please check the links below for additional details:

 

http://www.microsoft.com/technet/security/Bulletin/ms08-067.mspx
http://blogs.technet.com/msrc/archive/2008/10/23/ms08-067-released.aspx

 

How I’ve write in precedent post “use windows native command line for change attributes for multiple account” there are some useful Windows command Line tools that permit to do multiple activity in the same time.

 

In this example we explain how to use DSMOVE, a command line tool for move object in Active Directory.

 

Note: Only for remember this tip is valid for Windows 2000, Windows Server 2003, and Windows Server 2008.

 

User and computer accounts will be the types used most frequently from a mass management standpoint; Comma Separated Value Data Exchange (CSVDE) is a good starting point for an export file.

 

Scripting the move with dsmove is done via the command line.

 

Here is an example command that will move the username Jhon Buy from the Users OU to a new OU called DestinationOU:

 

 

dsmove "CN= Jhon Buy,CN=Users,DC=test,DC=Local" -newparent OU= DestinationOU, DC=test,DC=Local"

 

 

Note: When the DN of the object to move has a space, the entire DN is placed in quotes

 

 

When performing a multiple move, you may want to designate a domain controller with the -d parameter to process all of the transactions associated with the move to contain all of the work. Each dsmove operation is a direct call to the domain controller and could be taxing if the commands hit a relatively busy domain controller.

 

 

For create a .cmd script with more lines you can use Excel worksheet how I’ve specify in my precedent post here….

 

 

For more information please go to Microsoft Technet Site

 

This topic is necessary when you decide to redesign or plan a new naming convention in your domain for example, and the procedure is very different to rename a standalone server in the domain.

 

 

 

Many thanks to Daniel Petri that have write this article with the reference to rename Windows 2003 DC too.

 

 

 

This question has attracted my eyes a few times on different forums, so I decided to write an article about it. Choosing the right name for your servers is one of the steps that should be taken into account when designing a new network, or when deploying new servers. You should be totally aware of the names that you will assign each one of the new servers, and take naming conventions into consideration when designing a new network or a network expansion. However, in some cases, a simple typo or human error might cause the new server to get the wrong name. While easy to fix on regular servers, Domain Controllers should be renamed by using a different method.

 

 

 

 

 

 

The procedure of renaming a regular server (Windows 2000/2003/2008) is quite simple. It is done through the My Computer properties, and usually requires one reboot.

 

 

 

However, DCs should be renamed by using a totally different approach.

 

 

 

Note: This article focuses on Windows Server 2008 Domain Controller renaming. Although similar to the procedure done in Windows Server 2003 Domain Controllers, I would suggest that you please see the article titled "How can I rename my Windows 2003 Domain Controllers?". Also note that only Windows Server 2003 Domain Controllers can be renamed.

 

 

 

Another Note: Domain Controllers running Microsoft's Certificate Authority services (CA) can never be renamed.

 

 

 

Lamer Note: This is NOT the same as renaming your entire domain! For that, please use the RENDOM utility that is (now) a part of the Active Directory - Directory Services installed files.

 

 

 

The command

 

 

 

In order to rename a DC you will need the NETDOM command. In Windows Server 2008, this is part of the operating system, and not a separate download as in previous versions. By using the NETDOM command, you ensure that there is little or no disturbance for the domain and client operations.

 

 

 

Renaming a domain controller requires that you first provide a FQDN as a new computer name for the domain controller. All of the computer accounts for the domain controller must contain the updated SPN attribute and all the authoritative DNS servers for the domain name must contain the host (A) resource record for the new computer name. Both the old and new computer names are maintained until you remove the old computer name. This ensures that there will be no interruption in the ability of clients to locate or authenticate to the renamed domain controller, except when the domain controller is restarted.

 

 

 

Important: To rename a domain controller using the NETDOM command, the domain functional level must be set to at least Windows Server 2003.

 

 

 

The bad news: As usual, you will need to reboot the renamed DC.

 

 

 

The good news: You don't have to sit near the DC you're renaming. You can accomplish it from any computer that has the NETDOM command, and if you have the appropriate user credentials.

 

 

 

Permissions

 

 

 

You must be a member of the Domain Admins group.

 

 

 

To rename a DC with the name from KUKU-SERVER in the PETRI.LOCAL domain to DC-SERVER follow the next steps:

 

 

 

1. Open Command Prompt and type:

 

 

 

NETDOM computername KUKU-SERVER.PETRI.LOCAL /add:DC-SERVER.PETRI.LOCAL

 

 

 

This command will update the service principal name (SPN) attributes in Active Directory for this computer account, and register DNS resource records for the new computer name. The SPN value of the computer account must be replicated to all DCs for the domain, and the DNS resource records for the new computer name must be distributed to all the authoritative DNS servers for the domain name. If the updates and registrations have not occurred prior to removing the old computer name, then some clients may be unable to locate this computer using the new or old name. Therefore, it's very important to wait till the Active Directory replication finishes a replication cycle. You can check that by using tools such as REPADMIN and REPLMON.

 

 

 

You can verify the new name was indeed added to the computer object by viewing it through ADSIEDIT.MSC (which, for Windows Server 2008, is installed by default). Navigate to the computer object and right-click it. Select Properties:

 

 

 

Scroll down in the list of available attributes till you reach the attribute called msDS-AdditionalDnsHostName.

 

 

 

2. Ensure the computer account updates and DNS registrations are completed, then type:

 

 

 

NETDOM computername KUKU-SERVER.PETRI.LOCAL /makeprimary:DC-SERVER.PETRI.LOCAL

 

 

 

Again, you can inspect the change with ADSIEDIT.MSC. Scroll down in the list of available attributes for the computer object (notice how the server now appears with the new name) till you reach the attribute called msDS-AdditionalDnsHostName.

 

 

 

Notice that the old name should appear in the attribute's properties.

 

 

 

3. Restart the computer.

 

 

 

4. From the command prompt, type:

 

 

 

NETDOM computername DC-SERVER.PETRI.LOCAL /remove:KUKU-SERVER.PETRI.LOCAL

 

 

 

5. Make sure that the changes have successfully been replicated to all the DCs.

 

 

 

Conclusion

 

 

 

In this article, I have explained how to use the NETDOM command to rename Windows Server 2008 Domain Controllers. To see how this is accomplished in Windows Server 2003 Domain Controllers, see my article "How can I rename my Windows 2003 Domain Controllers?"