topic Re: Rapid Deployment Pack in ProLiant Deployment and Provisioning

Rapid Deployment Pack

Poekes — Mon, 27 Mar 2006 03:36:32 GMT

Hi,I have a problem with RDP.
When the server boot to automation, it is block to " initializing TCP / IP via DHCP ...... " in DOS
Somebody has already had this problem?
Thank you

Re: Rapid Deployment Pack

Jean-Yves Picard — Mon, 27 Mar 2006 09:44:17 GMT

Hello,

did you setup a DHCP server ?

with which parameter ?

is DHCP server connected to boot system ?

on same subnet ?

if no, did you provide IP helper ?

will you give points to folks helping you on RDP question ?

Jean-Yves Picard

Re: Rapid Deployment Pack

Poekes — Mon, 27 Mar 2006 09:58:13 GMT

Thank you for your answer,
I have a DHCP server with Option 60.
All server are in the same subnet

For example:
When I would like create an image, the server reboot, it restard in DOS and it blockt in "initializing TCP/IP via DHCP......."

Do you have another idea for this problem?

Re: Rapid Deployment Pack

dezizach — Mon, 27 Mar 2006 21:20:20 GMT

I just received my first Blade system and though I could get the first Blade deployed no problems, the remaining blades give me the same problem as this gentleman. Any clues?

Re: Rapid Deployment Pack

Poekes — Tue, 28 Mar 2006 06:27:09 GMT

Now, I have another problem:
When the server boot in DOS, it pass DHCP and after it don't find a drive!
"unable to map drive"

Re: Rapid Deployment Pack

Marcel Jussen — Tue, 28 Mar 2006 08:19:33 GMT

You might want to check your PXE enabled NIC. (Ctrl-S on boot).

I had this exact same problem. Autonegotiation between the NIC and the switch did not work as expected. Although our Cisco switch ports where preset to a 100Mb/FD setting the NC7781 cards failed to negotiate this setting.
While we used the autonegotiate setting the NIC was unable to receive a DHCP address 90% of the times the machine booted into automation. In the few cases an IP address was received other problems like imaging or server deployment failed or where dead slow.
When I set the NIC to a predefined setting (100Mb/Full Duplex in my case) the whole process worked like a charm.

You might want to give that a try and set the NIC speed to the required setting of your own network.

Cheers,
Marcel Jussen

Re: Rapid Deployment Pack

Albert Austin — Tue, 28 Mar 2006 13:29:17 GMT

Hi, I faced the exact same problem a few days ago. The strange thing was I was able to intial deploy my blades just fine but after I installing an OS using scripts, decided to create an image to deploy it to the other blades the process stopped exactly at the same phase and would give an error after sometime that could not get address from DHCP. We have been having some problems with our brand new switch so could not really pin point the fault. HP had their own solution for this error found here http://h18013.www1.hp.com/products/servers/management/rdp/knowledgebase/00000115.html
but this was of no help to my case. Hope it could help you in some way.

Re: Rapid Deployment Pack

Edwin.Scheurwater — Tue, 18 Apr 2006 13:11:01 GMT

We have seen it often that a client somewhere on the network thinks that it got a certain IP adress. By making a reservation for this IP address you're forcing the server which need to be deployed to ask for a "new" IP address.

The above has often be a solution when the TCP/IP initializing error ccurs.

Also make sure that DNS is configured correctly and that name resolution works. Also add the IP address of the RDP server in the LMHOST file of the PXE bootimage.

The other error that the drive is not mapped is probably caused by SMB signing. To avoid this the Lan Manager client properties should be adjusted on the RDP server. If this is still a problem let me know so i can send you the registry key to this.

Edwin

Re: Rapid Deployment Pack

Gordon Leonard — Wed, 19 Apr 2006 06:46:51 GMT

Other things to consider:

1) Ensure that the RDP server does not require SMB signing, by editing the following policy under the Local Security Policy MMC:
Security Settings - Local Policies - Security Options - Microsoft network server: Digitally sign communications (always) - set to "Disabled"

2) Ensure that the RDP server will store a LAN Manager hash for the eXpress share user account (PRIOR TO creating the account), by editing the following policy under the Local Security Policy MMC:
Security Settings - Local Policies - Security Options - Network Security: Do not store LAN Manager hash value on next password change - set to "Disabled"

3) Ensure that the RDP server will accept old-style LAN Manager connection authentication requests, by editing the following policy under the Local Security Policy MMC:
Security Settings - Local Policies - Security Options - Network Security: LAN Manager authentication level - set to "Send LM & NTLM Responses - use NTLMv2 session security if negotiated"

4) Create a local user account on the RDP server for accessing the eXpress share at this time. The system will save an LM hash for the account, and the DOS/Win98 client will be able to log in.

5) If the domain policy regarding LM hashes is enforced, then you will either need to ensure that the eXpress share user account password never expires, or else you will need to disable the LM hash policy temporarily (see #2) while you change the password for the user.

Re: Rapid Deployment Pack

Pradip Chakrabarti — Sat, 13 Jan 2007 10:23:22 GMT

Hi,

Can RDP s/w be installed on Windows server 2000 after OS hardening

If hardening is not there RDP is getting installed

Thanks in advance.