| Author |
Message |
![[Post New]](/Sysforums/templates/default/images/icon_minipost_new.gif) 27/05/2009 10:03:24
|
MachoMan
SysAider
Joined: 27/05/2009
Messages: 11
Offline
|
I'm having issues with Sysaid installed on a XenDesktop VM. The setup is the following: 30 VM streamed by a Provisionning with the same VDISK. When you deploy the sysaid agent .. only the last VM that we've deployed sysaid on is seen in the Asses List!
Might be normal since we are using the same vdisk for every VM but i still need a way to RC the VM for HelpDesk support through Sysaid!
Any ideas!??
|
|
|
27/05/2009 10:25:40
|
Mucho
SysAider
Joined: 13/05/2009
Messages: 48
Offline
|
I thing maibe this is because this 30 VM have same MAC Address.
|
|
|
27/05/2009 10:27:50
|
MachoMan
SysAider
Joined: 27/05/2009
Messages: 11
Offline
|
Well every single VM has it's own IP, MAC ADRESSE, and NAME!
|
|
|
27/05/2009 12:41:49
|
Joseph Zargari
VP Customer Relations
Joined: 26/03/2006
Messages: 516
Offline
|
This is a very interesting issue, actually.
Let me start by explaining how the SysAid agent used to work (version 5.6 or below) and how it is working today (version 6.0 or above).
In the past (until version 5.6.10), the SysAid agent used to take one of the MAC addresses and use that as a unique identifier for the asset (e.g. 00-11-22-33-AA-BB-CC). This could have caused a problem of multiple computers reporting into a single asset if they each had a NIC with the same MAC address. This was typical to computers that had virtual NICs (like VMware servers or computers with VPN clients).
Today (since version 6.0) the SysAid agent uses a more unique value for the asset ID. It uses the Manufacturer name and the computer serial number (e.g. DELL-aabbccdd ). If the computer is not branded (Dell, HP, IBM, etc) then it would work in the old way of choosing a MAC address as the unique identified.
So to further asset your situation, we would need to know:
1. What is version of the SysAid agent you are using to install?
2. Does it use the MAC address or the Manufacturer+Serial for the unique identified (it shows on the overwriting asset, in the header, next to the computer name in brackets)?
3. If MAC address: Is that address showing on all multiple computers (on any of the NICs)?
If Manufacturer+Serial: Is that information is actually the server manufacturer and serial, projected down to the guest machines?
Joseph.
|
|
|
27/05/2009 13:06:54
|
MachoMan
SysAider
Joined: 27/05/2009
Messages: 11
Offline
|
i'm Using Sysaid 6.0.04
it's using mac address
nope mac address is different on every single VM (ipconfig /all) ... the mac address showing in the Sysaid assets list is the one I use to built the Shared Vdisk with. To make it clearer It's not the mac address of the physical NIC of the XenServer but the autogenerated Mac Address of the virtual NIC of the VM.
As i try to redeploy SysAid on the virtual VM using the same vdisk, only the computer name is changing in the asset list.. .the mac address is staying the same as well as the serial.
Have you ever tested Sysaid with XenDesktop??
|
|
|
28/05/2009 04:04:57
|
Joseph Zargari
VP Customer Relations
Joined: 26/03/2006
Messages: 516
Offline
|
MachoMan,
SysAid was not tested by us on XenDesktop by us, but I do know of a few organizations that implemented this. XenDesktop creates virtual hardware, which SysAid considers as normal computers so there's no reason why it wouldn't work.
When SysAid agent is starting for the first time, it then chooses the MAC address to use as the unique ID and stores it in the registry (HKLM\Software\Ilient\Agent\MachineID). If you deploy it on top of an existing agent, it will see that a MachineID is already set and will skip that phase.
Looking at your last response, I realize that you installed the SysAid agent on one virtual desktop and then multiplied it. This would cause the registry on the initial desktop to already include the MAC address. When you copy that desktop, you copy the MachineID along with it. To avoid this you can use two solutions:
1. Don't put the SysAid agent on the initial computer. Copy the desktops without it and then deploy the agent onto the multiple machines. Alternately, you can undeploy the agent (to clear our the registry values) and only then deploy it again to the copied machines.
2. Install the SysAid agent on the initial computer and prepare the registry values to the copying of the virtual desktop. Before copying it, go to HKLM\Software\Ilient\Agent and delete the MachineID value. Also change the FirstTime value to Y. This will make the agent create a new MachineID the next time it would start (at each and every new desktop).
Joseph.
|
|
|
28/05/2009 10:01:21
|
MachoMan
SysAider
Joined: 27/05/2009
Messages: 11
Offline
|
Joseph
About solution 1
I'm not quit sure about this solution because, if we deploy sysaid only on the multiple machine, every single time a user logged off a VM, the VM restart and the provisionning streams back the image of the VDISK that has not SysAgent on.
About Solution 2
I though it was a great idea but i'm getting this error
Type de l'événement : Erreur
Source de l'événement : Application Error
Catégorie de l'événement : Aucun
ID de l'événement : 1000
Date : 2009-05-28
Heure : 09:51:02
Utilisateur : N/A
Ordinateur : XPWITHOFFICE2
Description :
Application défaillante ilias.exe, version 2.2.0.32, module défaillant ilias.exe, version 2.2.0.32, adresse de défaillance 0x00001c17.
Pour plus d'informations, consultez le centre Aide et support à l'adresse http://go.microsoft.com/fwlink/events.asp.
Données :
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 69 6c 69 ure ili
0018: 61 73 2e 65 78 65 20 32 as.exe 2
0020: 2e 32 2e 30 2e 33 32 20 .2.0.32
0028: 69 6e 20 69 6c 69 61 73 in ilias
0030: 2e 65 78 65 20 32 2e 32 .exe 2.2
0038: 2e 30 2e 33 32 20 61 74 .0.32 at
0040: 20 6f 66 66 73 65 74 20 offset
0048: 30 30 30 30 31 63 31 37 00001c17
0050: 0d 0a ..
|
|
|
28/05/2009 13:38:40
|
MachoMan
SysAider
Joined: 27/05/2009
Messages: 11
Offline
|
Forget about the error ... you just need to reboot the Master VM after deploying Sysaid on it and then modify the register.. .after that it works like charm!
You also have to make sure that the Deploy Agent Settings "Generate Random Asset ID" is not checked because you're going to end up with a whole lot of asset into your asset list as it's going to generate a new asset every single time a multiple VM that is rebooted!
One last question ... when a user creates a task, the name of the asset do not automatically attach to the created task... it there a way to make sure it does??
This message was edited 1 time. Last update was at 28/05/2009 16:11:21
|
|
|
31/05/2009 03:08:53
|
Haim
SysAid Wiz
Joined: 15/04/2008
Messages: 2449
Offline
|
MachoMan,
To make the asset's name automatically assign to the service request, the user need to use the desktop shortcut or the hot key. This way, the agent will open the service request page and assign the appropriate asset name.
Best regards.
Haim
|
Pushing IT forward |
|
|
![[Up]](/Sysforums/templates/default/images/icon_up.gif){kind=icon}
