HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- ProLiant Deployment and Provisioning
- >
- Deploying 64 bit windows with RDP 3.10
ProLiant Deployment and Provisioning
1833035
Members
2195
Online
110049
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2006 02:57 AM
12-02-2006 02:57 AM
Deploying 64 bit windows with RDP 3.10
do we still need to use the sysprep in imaging & deploying 64 bit windows with RDP 3.10 as follows?
any help is highly appreciated.
How To Image Windows 2003 x64 Using Sysprep
Article: 170
Applies to: Release 3.00
The following steps will install jobs and support for Windows 2003 x64 sysprep imaging.
1. Sysprep Support Files a. Create the directory .\sysprep\dotnet if it does not already exist.
b. If the file deploy.cab already exists in the above directory, rename it to deploy.2003.
c. From the Windows 2003 x64 CD, copy the \support\tools\deploy.cab file to the above directory.
NOTE: The current version of Deployment Server can only support one sysprep file at a time. When you are done with Windows 2003 x64 sysprep, rename this file back to the original filename.
2. ProLiant Support Files a. Create the directory .\lib\osoem\proliant.751\w52.64.
b. From the Rapid Deployment Pack 3.00 DVD, copy the \extras\proliant751-w52.64 directory to the new directory.
3. Console Options a. In the Deployment Server Console, select Tools > Options.
b. Select on the Global tab. Click on the Sysprep Settings button.
c. Click on the Sysprep Settings button.
d. In the Licensing Information group, input values for User Name, Organization Name, and Licensing Mode.
NOTE: This is to workaround an issue in the current version of Deployment Server. These values will not be used.
4. Jobs a. In the Deployment Server Console, in the Server Replication job folder, import the two .bin files located on the Rapid Deployment Pack 3.00 DVD in the \extras directory.
b. In the Read ProLiant ML/DL/BL Windows 2003 x64 Sysprep Image {WinPE} job, modify the Create Disk Image task. Add your Windows 2003 x64 product key.
b. In the Write ProLiant ML/DL/BL Windows 2003 x64 Sysprep Image {WinPE} job, modify the Distribute Disk Image task. Add or select your Windows 2003 x64 product key.
any help is highly appreciated.
How To Image Windows 2003 x64 Using Sysprep
Article: 170
Applies to: Release 3.00
The following steps will install jobs and support for Windows 2003 x64 sysprep imaging.
1. Sysprep Support Files a. Create the directory .\sysprep\dotnet if it does not already exist.
b. If the file deploy.cab already exists in the above directory, rename it to deploy.2003.
c. From the Windows 2003 x64 CD, copy the \support\tools\deploy.cab file to the above directory.
NOTE: The current version of Deployment Server can only support one sysprep file at a time. When you are done with Windows 2003 x64 sysprep, rename this file back to the original filename.
2. ProLiant Support Files a. Create the directory .\lib\osoem\proliant.751\w52.64.
b. From the Rapid Deployment Pack 3.00 DVD, copy the \extras\proliant751-w52.64 directory to the new directory.
3. Console Options a. In the Deployment Server Console, select Tools > Options.
b. Select on the Global tab. Click on the Sysprep Settings button.
c. Click on the Sysprep Settings button.
d. In the Licensing Information group, input values for User Name, Organization Name, and Licensing Mode.
NOTE: This is to workaround an issue in the current version of Deployment Server. These values will not be used.
4. Jobs a. In the Deployment Server Console, in the Server Replication job folder, import the two .bin files located on the Rapid Deployment Pack 3.00 DVD in the \extras directory.
b. In the Read ProLiant ML/DL/BL Windows 2003 x64 Sysprep Image {WinPE} job, modify the Create Disk Image task. Add your Windows 2003 x64 product key.
b. In the Write ProLiant ML/DL/BL Windows 2003 x64 Sysprep Image {WinPE} job, modify the Distribute Disk Image task. Add or select your Windows 2003 x64 product key.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2006 01:42 AM
12-08-2006 01:42 AM
Re: Deploying 64 bit windows with RDP 3.10
I seem to recall it will use SYSPREP still (do not install it as part of the RDP setup - RDP it place it in latter, just skip the part where it ask for SYSPREP). You do not need to follow the noted steps since it is all automated now.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP