- This topic has 7 replies, 2 voices, and was last updated 6 years, 6 months ago by ConfGen.
-
AuthorPosts
-
October 18, 2017 at 8:12 pm #45477
Just tried to install WDM 5.5 on fresh Win7x64 installation. When launching WDM, I get two error notices in the Service Logs:
Source: GUI; Description: unable to find standard service at server 0.0.0.0 and port 8008.
Source: Testing Connections; Description: Failed to connect to WDM (DHCP)
In the Component Details Report, all components are set to the WDM server IP, except for Standard Services which is showing 0.0.0.0
In addition, HServer is not starting automatically, though it’s set that way. I have to manually start it.
I’ve done this twice, reverting to the fresh Win7 installation for the second try. First I simply ran the WDM 5.5 installer, the second time I configured IIS prior to running the 5.5 installer, according to the details provided in the WDM 4.9.1 Install Guide. Same outcome.
Any thoughts on what went wrong?
October 20, 2017 at 4:47 pm #45489Why do you try to install such an old version of WDM?
Use 5.7.2!CG
October 21, 2017 at 8:19 am #45491Software requirement for 5.7.2 changed to Win 7 x64 Enterprise from Win 7 x64 and I have Ultimate on the PC I use for WDM.
I will try 5.7.2 anyway.
I regularly have used “roll to boot” to recover problem devices or install new boot drives, using 4.9.1, and I see that it uses TFTP during this process. Do I need to specify the TFTP option, as well as HTTP, during installation (Workplace version)?
October 21, 2017 at 10:04 am #45492You can select wether to install or not TFTP during install. That’s all you have to do.
No difference between the requirements. Enterprise or Ultimate – both will work.CG
October 21, 2017 at 10:25 am #45493Is the TFTP selection needed for “roll to boot” to work?
October 21, 2017 at 4:55 pm #45494Today most clients have a boot agent. Therefore, PXE with TFTP is not needed.
To be sure, install TFTP. It will not harm if you install it.CG
October 25, 2017 at 10:58 pm #45509Thanks for the suggestion, 5.7.2 is running now.
For a couple of 7020 series clients with older HAgents, when they check in and I do the HAgent update, the update appears to work OK so far as WDM is concerned, but the client hangs at the blue screen indicating update in process. I can shut the client down, and reboot fine.
Also, how do I log in to the WebUI? I cannot figure out what credentials are required. The server and repository credentials specified during installation don’t work. There is currently no password specified for the server user account itself, yet the WebUI requires a password to use the user account name.
October 26, 2017 at 2:38 pm #45516Log in to the webui is done with one of the user accounts that are listed under Configuration Manager – User Permission.
Open the WDM MMC console to check that.
Typicially it is always the user account that was logged in to the Windows system while installing WDM.CG
-
AuthorPosts
- You must be logged in to reply to this topic.