Which, if any, of the WHQL licenses do I have to sign in order to be able to get DTM configured properly?
I have spent 2 1/2 days now trying to get the client and controller to see each other with no success and am somewhat frustrated.
I am using WLK 1.6.
The two computers are:
On the same network
In the same workgroup
Have static IP addresses
Can wttcmd /ping each other
Can copy files between each other using the network explorer
I followed all of the instructions that were relevant my my situation (Workgroup installation not Domain). I installed the client over the network from the controller network share, as per the instructions, yet for some reason the client and controller cannot see each other.
I have tried with the Windows Firewall on and off with no success.
I have tried the DTM client on Windows 7-x32 and Windows 7-x64 with no success.
What am I doing wrong here?
It should not be this hard for the client and controller to connect.
There should be some manual connection method where I can get the client to locate the server and say ‘connect’ instead of the is ‘automated’ sit on your hands and wait mode.
Why can it take up to 20 minutes (I wish) to make what amounts to a TCP/IP connection; what is it doing?
Peter Young
> Which, if any, of the WHQL licenses do I have to sign in order to be able to
get DTM configured properly?
None of them - your DTM setup is completely independent of your WHQL and Winqual status. There is even a separate program, called Winqual Submission Tool, as a stepping stone from your DTM results to the next stage of the WHQL process.
I am using WLK 1.6.
I have tried the DTM client on Windows 7-x32 and Windows 7-x64 with no
success.
Shame I cannot recommend you try WLK 1.5 as Microsoft have probably deleted it, plus it would only be a stop-gap measure until the end of May. I have only just started testing WLK 1.6 on a couple of separate test PCs before completely committing to the new version. So far I have only tested on an XP client because I knew it would be the quickest. You said last week you need to test on XP through to Server 2008 R2, so give XP a go and let us know how you get on.
On the same network
Is it a private network, or your general office network? Not that it should make much difference, but choosing a private network with just the DTM suit eliminates potential interference.
Good luck,
Tim.
May be a trivial thing, but can you check if your “machine query” in DTM studio is setup correctly? You can start by having only the
field name “Machine pool path” and see if this helps.
I had struggled for a day just to get the client listed in the DTM studio, before realizing that this setting was incorrect.
Dear Peter Young,
I use WLK 1.5 with a Windows 2003Server OS, If I suppose this new version have the same install process.
Have you got installed the DTMStudio part before install the DTMController ?
Try to reinstall the WLK.
My configuration :
Install clean OS
create a workgroup and add all machine into
Add static network config
to target : Add IPV4 adress and the gate with ip adress of the Studio/Controller machine.
Install DTMStudio and DTMController to the same machine.
Install DTMClient to target machine.
Normally, if you lanch DTMStudio , select “JobMonitor” the target machine must appear in “Default pool”.
hoping have you helped
Best regards,
Moulefrite
Thanks for all the advice and ideas.
I think the problem was the machine query.
If I specifically add query clauses for each machine I want to test against then suddenly, as if by magic, they appear in the list and I can add them to my test pool.
Now for the messy part, running the actual tests.
Peter Young