- This topic is empty.
-
Posts
-
I am just starting on a new project placing WDM 4.5.3 on a Win2K3 R2 server with SP1 already installed. The database is on a separate SQL 2005 server that is also on Win2K3 R2/SP1. I had to manually install the database prior to installing WDM 4.5.3 in order for the install to finish.
Right now I have 2 devices that already had images from the 4.4.1 Rapport server that was upgraded to 4.5.1. The old server was on a win2K build and my work has a mandate to move to Win2K3. The 2 devices are an old 9455 and a V90. Discovery did not work so I had to add the devices manually to WDM. I have not yet been able to image the devices or have them obtain the IP address that I have assigned to the devices when I added them.
I am a greenhorn when it comes to WDM. I was just given this project when the person who normally handles WDM switched to another account. I have not one clue on how to proceed.
The 2 devices and the servers are connected via Cisco switches. SpanningTree and PortFast is enabled and for good measure IP helpers are set up on the routers in the lab. The servers were built in VMWare.
Where am I going wrong here?
Couple of questions:
Is the older WDM server still online?
Does the new WDM server carry the same IP address as the old WDM server?
What happens if you manually enter the new WDM server IP address in the XPe control panel WDM applet?The new server is in a testing lab and isolated from the old servers. The IP address is completely different. When I added the IP address into the Rapport applet in Control Panel on the device, nothing really changed. It would not gain the assigned address during either boot or after an automatic login.
Only thing I noticed is that when the device booted, the DHCP message I would get is “proxyDHCP offers were received. No DHCP offers were received.”
One last thing. On the DHCP log in the WDM Service Logs, I am getting an error of “Either HServer address or port is null – cannot respond to RTI device”.
OK, the sever has an issue. WDM pulls the port from IIS so make sure IIS is running correctly. Also make sure you set Windows DEP to “essential windows programs and services” or it will block IIS and hence stop WDM. Get to this from Properties My Computer – Advanced – Performance Settings – Data Execution Prevention.
While you are at it make use the Rapport local user on WDM server has its password set to never expire,
Cheers,
-TTDEP was not set properly so I fixed that and I had the Rapport account already set to never expire. When I restarted the server, I no longer got any error messages in the WDM Services Logs. However, no improvement has occured in discovery or DHCP functionality.
Is DHCP on a seperate server in the lab to the WDM server? It needs to be. When you restart the client do you still get the DHCP Proxy error?
I still get the “proxyDHCP offers were received. No DHCP offers were received” error.
Also, I didn’t load DHCP separately. I was under the assumption that WDM also had it’s own DHCP service built in.
Ahh, there is the problem. WDM is not a DHCP server, its a PXE server.
Can you set up a DHCP server on a different box or router? Don’t put it on the WDM box as PXE and DHCP use the same ports so this will cause you issues,
Cheers,
-TTIt appears that DHCP was actually up and running on one of the over servers in the lab, except it was configured to look at a different VLAN for client machines. I moved the thin clients to that VLAN and the devices are no longer getting DHCP errors on PXE boot.
However, I am still unable to image or even discover the devices on VDM. Right now, the WDM server, the DHCP server, and the client devices are all on separate VLANs.
OK,
Can you put the Device and WDM on the same VLAN and configure the DHCP server to provide IP’s to the VLAN. Once this works we can move out to putting devices on different VLAN’s, you will need to add a IP helper to the VLAN interface pointing back to the WDM server to image over VLAN’s,
Cheers,
-TTI have been continuing with my troubleshooting efforts and am stumped. One common symptom is occuring that I have found that has me baffled.
Regardless if I have the RAPPORTDB on a separate SQL box or on the same box that WDM is on, the record in the Server table for port 80 is not being created.
I have tried reinstalling the RptStdSvc, I have tried having the server in an OU without any GPOs, and I even tried manually adding the record. Nothing so far has allowed me to get discovery to work properly. DHCP is working fine and the device is not even getting the proxyDHCP error anymore. However, discovery does not work and I can’t push any packages to a device if I manually add it.
The servers are Windows 2003 with SP2 installed with a basic IIS configuration with FTP and WWW installed. SQL is the 2005 version. DEP is set for only essential services.
OK, so you have been uninstalling and re-installing? This makes it hard to nail the problem if the configuration keeps changing so maybe settle on one build and lets work with that.
The location of the DB will have no bearing on the discovery so use whatever makes sense to you. If you are using workgroup WDM you must use the DB locally.
Can you look in the application log of the server, are there any errors relating to the web service or Hserverinit? Let check the server is working.
Also you were going to post back the results of having a terminal on the same subnet as the WDM server, can you try this and let me know the results? Remember your DHCP server will need to be able to issue IPs to the subnet with WDM and the device.
Cheers,
-TT
- You must be logged in to reply to this topic.