Showing posts with label r2. Show all posts
Showing posts with label r2. Show all posts

Wednesday, July 11, 2012

How to Install Windows Storage Server 2008 R2 and the Microsoft iSCSI Software Target 3.3

How to Install Windows Storage Server 2008 R2 and the Microsoft iSCSI Software Target 3.3


Overview
You probably heard that Windows Storage Server 2008 R2 has been Released To Manufacturing (RTM) last week.
That means that the OEMs will soon deliver a new generation of Windows-based NAS appliances with a file server (SMB2, NFS) and an iSCSI Target (using the Microsoft iSCSI Software Target 3.3).

clip_image001


What you might have missed is that Windows Storage Server 2008 R2 is also now available to MSDN and TechNet subscribers for evaluation. This means subscribers can now use the Microsoft iSCSI Target 3.3 for Development, Test and all other non-production purposes.
While this was also the case for Windows Storage Server 2008, this new R2 release allows you to install the iSCSI Target on any existing Windows Server 2008 R2 by simply installing an MSI (Microsoft Installer) file. That’s much more convenient for Developers, Testers and IT Profressionals out there.
Usage Scenarios
Here are a few things you could do with the Microsoft iSCSI Software Target:
  • Setup a test environment for Hyper-V (using Windows Server 2008 or Windows Server 2008 R2) using iSCSI shared storage.
  • On a single laptop (with enough resources) create a development environment running a SQL Server cluster (two nodes, plus shared storage).
  • Evaluate Windows Server 2008 R2 Cluster Shared Volumes (CSV) and Hyper-V Live Migration, using only regular Windows Server hardware.
You are probably thinking of a few other ways to use this. If they are for evaluation (TechNet Plus or MSDN), demonstration (MSDN), development (MSDN) or test (MSDN), they are probably good scenarios as well.
Download
Find below the information from the MSDN/TechNet site where you download the bits:
  • Name: Windows Storage Server 2008 R2 Embedded (Standard, Enterprise, Workgroup) with iSCSI Software Target 3.3 (x64) - DVD
  • Size: 947 (MB)
  • File Name: mu_windows_storage_server_2008_r2_embed_stand_ent_work_with_iscsi_software_target_3.3 _x64_dvd_587719.iso
  • Date Published (UTC): 9/27/2010 3:01:52 PM
  • Last Updated (UTC): 9/27/2010 3:01:52 PM
  • SHA1: CAC10773B6DD63FD397F5F00252B252CAF70EE40
  • ISO/CRC: 0C19C89F
  • Instructions and Resources: You must first install Windows Server 2008 R2 before installing this product. The license agreement for this product references a 180-day term. This download will retain full functionality even after 180 days. The following languages are included in this download: Chinese-Simplified, Chinese-Traditional, English, French, German, Italian, Japanese, Korean, Portuguese-Brazil, Russian, and Spanish.
No keys are required for this download.
Unpacking
The file you will find on MSDN/TechNet is, as you saw above, an ISO file. To look inside of that, you can burn that ISO file to a physical DVD or use one of the many tools that can mount an ISO image as a virtual DVD.
Inside that ISO file there is an executable file (Windows_Storage_Server_2008_R2+iSCSI_SW_Target_33.exe), which you need to run to unpack the two ISO files inside (iSCSI_Software_Target_33.ISO and Windows_Storage_Server_2008_R2.ISO).
Inside the iSCSI_Software_Target_33.ISO file, in the x64 folder, you will find three MSI files, one of which is the only file that you really need to install the iSCSI Target, called iscsitarget.MSI.
To help you understand the installation process, here’s a little diagram of the required steps to unpack and deploy Windows Storage Server 2008 R2 from that executable file.
Understanding the Files
To be clear, here are the names of the outer ISO (the file you download from MSDN/TechNet), the EXE file and the two inner ISO files:
  • mu_windows_storage_server_2008_r2_embed_stand_ent_work_with_iscsi_software_target_3.3 _x64_dvd_587719.iso
    • Windows_Storage_Server_2008_R2+iSCSI_SW_Target_33.exe
      • iSCSI_Software_Target_33.iso
      • Windows_Storage_Server_2008_R2.iso 

Install just the iSCSI Target
If you’re installing the just iSCSI Target on a virtual machine, you can just mount the iSCSI_Software_Target_33.ISO file as a virtual DVD and run the \x64\iscsitarget.msi file inside it.
If you’re running the target on a physical server, you can burn the iSCSI_Software_Target_33.ISO file to a physical DVD or use one of the many tools that can mount an ISO image.
Another option for physical server is to copy the jut the iscsitarget.MSI that’s inside iSCSI_Software_Target_33.ISO file to a USB disk or file share and install from there.

How to install Storage Server ?


Step 1: Install Windows Server 2008 R2 on the reference computer (use Windows Server 2008 R2 Standard as the basis for the Workgroup and Standard editions of Windows Storage Server 2008 R2, and use Windows Server 2008 R2 Enterprise as the basis for Windows Storage Server 2008 R2 Enterprise) Step 2: (Optional) Install language packs. Windows Storage Server 2008 R2 supports 11 languages.

Step 3: Install the Windows Server 2008 R2 operating system updates that are provided in the Windows Server 2008 R2 OPK. Step 4: Install the storage server-specific features that are provided in the Windows Server 2008 R2 Application Pack. Step 5: Add and configure the Remote Desktop Protocol (RDP) website. This enables access to storage appliances over a network. Step 6: (Optional) Add performance-specific registry keys. These keys increase the performance of the storage appliance when it is used as a file server. Step 7: (Optional) Set Windows PowerShell™ execution policy. This policy must be enabled if you customize the end user setup experience. Step 8: Enable Windows Remote Management. This policy must be enabled if your storage appliance will be part of a failover cluster. Step 9: (Optional) Install non-Microsoft applications. Complete this task only if your end users need to use custom applications to set up or manage the storage appliance. Step 10:(Optional) Add your OEM software license terms in all the supported languages. If you need end users to accept your software license terms during the appliance setup, you need to add the agreement to your installation.



Tuesday, May 8, 2012

SCCM Capture Media not able to Capture Reffrence Computer image.

When trying to capture a new image of DELL Optiplex 790 windows 7 Proff SP1.  After I fill in the relevant information to save to a network share on a SCCM Server itself and then select finish, the windows disappears and does nothing.
i looked for Sysprep Folder in %System Drive %\windows32\Sysprep but it was present and able to run properly.
Checked Computer Network Access Account on SCCM Server and for Local Computer also then after
  i have looked at the logs and this is what it states:

AllocateCDRoms is set; will not start TSManager

This seems to halt the capture process and nothing else happens.
i have also plugged in an external drive to capture the image to this, and the same error comes up.

Cause :

AllocateCD Rome is Restricted by Group Policy when it was in Domain or by default set by some OEM vendors.

SCCM Capture media uses SYSTEM and Domain Account for Capturing the Windows Image but GPO is only allow CD ROM access to Logged on Users in result Capture wizard Finished without any capture process.

Resolution :

"allocatecdroms" is the REG Key value which is responsible for the CD ROM access.

By default the Value is "0" if this value is "1" that means CD ROM access has been restricted for Local logged on users only.

To resolve this issue set REG Key value to Default "0" and save it.

close Regedit and Restart Computer.

Start Capture wizard again and check...

For More information Please browse Microsoft Technet Article for the same...

http://technet.microsoft.com/en-us/library/cc957388.aspx

Cheers!!!!!

exchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter

Wednesday, May 2, 2012

Windows Deployment Service Fail to start in 2003 and 2008 with SCCM

Windows Deployment Service Fail to start in 2003 and 2008 with SCCM.

I have a Windows 2008 Server that has WDS + SCCM 2007 R3 installed.  The Windows
Deployment Services Server Service isn't started and when I try to
Start  it I got a message that says:

Windows could not Start the Widows Deployment Services Server on Local
Computer.  For more information, review the System Event Log.  If this
is a non-Microsoft service, contact the service vendor, and refer to

server-specific error code 2310.
Event viewer lists Event ID 257 and this:
An error occurred while trying to Start the Windows Deployment Services
server.
 Error Information: 0x906
  
Hear is the Problem Analysis and Resolution of below errors.

CAUSE :

This problem occurs because the location of the computer object that is running WDS has changed in the Active Directory directory service.

A Windows Deployment Services (WDS) server is running Microsoft Windows Server 2003 with Service Pack 1 (SP1) or Microsoft Windows Server 2003 with Service Pack 2 (SP2). If you move the WDS server to a different organizational unit, the WDS server may not start. Additionally, one of the following error messages may be logged in the System log on the WDS server:

Error Messages :

Error message 1
Type: Error
Event ID: 7024 Source: Service Control Manager
Description: The Windows Deployment Services Server service terminated with service-specific error 9 (0x 3).
exchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter Error message 2
Type: Error
Event ID: 7024 Source: Service Control Manager
Description: The Windows Deployment Services Server service terminated with service-specific error 19 (0x13)
One of the following groups of error messages may also be logged in the Application log:

Error message group 1

Type: Error
Event ID: 261
Source: WDSPXE
Description: An error occurred while trying to initialize provider BINLSVC loaded from C:\WINDOWS\system32\binlsvc.dll. If the provider is marked as critical the Windows Deployment Services server will be shutdown. Error Information: 0x 3

Type: Error
Event ID: 1800 Source: BINLSVC
Description: An error occurred while creating the Service Control Point object for this Windows Deployment Services server in Active Directory Domain Services. Error Information: 0x 3

Type: Error
Event ID: 1803
Source: BINLSVC
Description: An error occurred while attempting to locate the Service Control Point object for this Windows Deployment Services server in Active Directory Domain Services. There was an error reading the 'netbootSCPBL' attribute from the Computer object. Error Information: 0x2
Error message group 2

Event Type: Error
Event Source: BINLSVC
Event ID: 1803 Description: An error occurred while attempting to locate the Service Control Point object for this Windows Deployment Services server in Active Directory Domain Services. There was an error reading the 'netbootSCPBL' attribute from the Computer object. Error Information: 0x2

Event Type: Error
Event Source: BINLSVC
Event ID: 1800 Description: An error occurred while creating the Service Control Point object for this Windows Deployment Services server in Active Directory Domain Services. Error Information: 0x13

Event Type: Error
Event Source: WDSPXE
Event ID: 261 Description: An error occurred while trying to initialize provider BINLSVC loaded from C:\WINDOWS\system32\binlsvc.dll. If the provider is marked as critical the Windows Deployment Services server will be shutdown. Error Information: 0x13

Event Type: Error
Event Source: WDSPXE
Event ID: 265 Description: An error occurred while trying to initialize provider BINLSVC. Since the provider is marked as critical, the Windows Deployment Services server will be shutdown. Error Information: 0x13

Event Type: Error
Event Source: WDSServer
Event ID: 513 Description: An error occurred while trying to initialize provider WDSPXE from C:\WINDOWS\system32\wdspxe.dll. Windows Deployment Services server will be shutdown. Error Information: 0x13

Event Type: Error
Event Source: WDSServer
Event ID: 522
Description: An error occurred while trying to shutdown provider WDSPXE. Error Information: 0x6

RESOLUTION :

To resolve this problem, reinitialize the WDS server after you move the WDS server to a different organizational unit. To do this, follow these steps:
  1. Click Start, click Run, type cmd, and then click OK.
  2. At the command prompt, type wdsutil /uninitialize-server, and then press ENTER.
  3. Move the WDS account to Active Directory in the new organizational unit.
  4. To reinitialize the WDS service, type wdsutil /initialize-server /reminst:{RemoteInstallFolder} at a command prompt, and then press ENTER.

Enjoy!!!!