[Computer name - Missing feature , Citrix XenApp]

Hi Guys

 

We have had resolved this issue by an accident. What we have done is we have had swapped over NIC settings in HyperV when we took VMs from HyperV2 to HyperV3 so now interface 0 is a Provisioning network, interface 1 is our domain network. I have realized that it is working fine after a few days really :]

 

I think it was HyperV's thing messed up rather than PC Monitor's one and perhaps that's why it was so difficult really to pin point it. Anyways, thanks for support on this one, and very best regards.

 

Raf

[Computer name - Missing feature , Citrix XenApp]

You mean that you are pushing the same ComputerIdentifier to all of the virtual machines. This is bad. Make sure you don't change the ComputerIdentifier.

 

I think that the service changes it when starting on the boot up, but I could be wrong.

[Computer name - Missing feature , Citrix XenApp]

They have all got changed for new REG_SZ values except the one on the Developement server.

 

 

Is there any way to have this resolved ?

[Computer name - Missing feature , Citrix XenApp]

Hi

 

I have written down values of the ComputerIdentifier from the development server and two production servers so tomorrow when they are freshly rebuild   again overnight will check in the registry if these values got changed and if this is creating problem.

 

I also think that I wasn't removing this ComputerIdentifier item from registry when I was pulling off the image, just ComputerName field was deleted.

We will see tomorrow then. Thanks. 

 

Raf

[Computer name - Missing feature , Citrix XenApp]

Hi Again

 

Sorry for being a pain, but infos about these servers is being multipied overnight after when they are rebuild, I will include a photo for you guys to have perspective. 

[Computer name - Missing feature , Citrix XenApp]

Ok, now it works fine.

 

So to sum this all up together:

 

 

On development server:

 

1- stop PC Monitor Service

2 - delete registry entry:  HKEY_LOCAL_MACHINE\SOFTWARE\MMSOFT Design\PC Monitor\ComputerName

3 - Pull off master image

4 - Distribute that image across production servers

5 - have a doughnut :]

 

 

Thanks for help resolving this guys. Kind Regards.

 

 

Raf

[Computer name - Missing feature , Citrix XenApp]

Sorry, my bad, just had too many remote sessions windows open.

 

So... after I did what was suggested, it is still showing up development server's name in the PC Monitor.

[Computer name - Missing feature , Citrix XenApp]

Thanks for your answer. 

The name that PCMonitor Manager is picking up now is the name of Hyper-V host that Development/Production Servers are running on. So it seems it does not solve the issue.

Any other ideas ? Thanks.

 

 

Raf

[Computer name - Missing feature , Citrix XenApp]

Howdy!

 

 

When we use PC Monitor in Cirtrix XenApp environment, on our production servers value of ComputerName is being copied from master image on which we have PC Monitor installed and then the image was distributed between these production servers. 

 

Manual change is not a problem if to be done once, but due to the fact these production machines are being rebuild every night according to master image - using PC Monitor to monitor XenApp servers adds daily task to our busy jobs.

 

What I think should be available in PC Monitor Manager on the Account tab/Computer Information/Computer Name is a tick box to use %Computername% queried (on the startup) against registry of actual machine rather than string entry only.

 

 

Thanks for consideration of proposed improvement of your product.

 

 

Kind Regards

Raf