New to View. Created a desktop pool and noticed they had two LUNs attached, wondered why. Looks like the second one may be because the original master had a CD iso attached.
In order to remove this from all the clones, do I need to make the change (disconnect the cd) from the master and then recompose?
Thanks
You can either make the change on the master and recompose or you can just script the change on the clones as a stopgap until you push out another image.
That's what I thought - thanks!
I think the decision lies in what you are more comfortable with and what you may already have setup. The users who are upgrading from previous versions that already have events databases configured may stay with that where as someone who is new and has existing syslog infrastructure may opt for that method.
OK, so thery both log the same thing then. Perfect. Thanks!
danh2010 wrote:
OK, so thery both log the same thing then. Perfect. Thanks!
sweet - I did not know that 5.2 moved away from requiring a database for events logging - syslog strikes me as a MUCH better alternative ....
It doesn't....I just swapped one of my View servers and it alerted me that I don't have an event db in place.
That's ridiculous. If I am logging by syslog, why should it care if I don't have an events db in place?
danh2010 wrote:
It doesn't....I just swapped one of my View servers and it alerted me that I don't have an event db in place.
That's ridiculous. If I am logging by syslog, why should it care if I don't have an events db in place?
ahhh ...
well then it must be as it has been: events logging is very detailed, and correlates user and desktop activity, and etc ...
I think syslog is more general "system level" logging that does not capture user and/or desktop level activity ....
*I think*
I've got them both turned on now. Our auditors are sticklers.
Page 122 of the install guide, http://pubs.vmware.com/view-52/topic/com.vmware.ICbase/PDF/horizon-view-52-installation.pdf, states "You can generate View events in Syslog format so that the event data can be accessible to analytics software". It sounds to me like it would be the same information. Maybe once someone has it setup and working correctly they can confirm the consistency of the data between events database and syslog format.
OK, but once the Log to File is enabled, will View automatically send this info to the syslog server AND not generate an alert for the Event db?
My tests show no, still alerts.
We had that issue and it was related to SSO. You can setup the username for the vcenter server as domain\user or setup SSO domain lookup order...
Hi Team...
I'm stuck getting off the ground with VMW View.
I've got my first linked clone pool ready to go (no errors).
Its provisioned and users are entitled.
I try to reach out using the VMware View client for Win32,
and I get this: http://screencast.com/t/4lo3kWcYm
I've seen some articles about it, but nothing is jumping out at me.
Here are the two screenshots of my View client log files:
http://screencast.com/t/wHa8gPFDodIR
and (attached)
It looks good until the end, where it just explodes in a 400... Thanks in advance.
PS: I took a screenshot of my vCenter install / ports at install time for reference. I didn't change anything: http://screencast.com/t/tDDIkyZsxVAc
"
2013-06-21T17:05:32.281-04:00 INFO (0388-04BC) <Main Thread> [wswc] Windows Client started 2013-06-21T17:05:32.296-04:00 DEBUG (0388-0810) <InitUIManager> [MessageFrameWork] MessageFrameWork Worker Added, Name=UIManager, Description=Provides User Interface services for a session, Channel=00000000 2013-06-21T17:05:32.296-04:00 DEBUG (0388-0818) <NodeManagerWatcher> [MessageFrameWork] Outgoing SharedMemory channel from wswc to machine Win7Computer-32 wsnm connected as : WIN7COMPUTER-32\Administrator, Authenticated through SSPI, package = NTLM, encrypting = true 2013-06-21T17:05:32.296-04:00 DEBUG (0388-0818) <NodeManagerWatcher> [MessageFrameWork] Connection to Node Manager established. 2013-06-21T17:05:32.312-04:00 DEBUG (0388-0804) <PluginInitThread> [MessageFrameWork] MessageFrameWork Worker Added, Name=GuestUIManager, Description=The in-guest UI management service, Channel=00000000 2013-06-21T17:05:32.312-04:00 DEBUG (0388-0820) <connectThread> [wswc_ui] CanLoginAsCurrentUser: client not in domain 2013-06-21T17:05:33.578-04:00 DEBUG (0388-0764) <MessageFrameWorkDispatch> [wswc_http] Broker request brokerConnect started 2013-06-21T17:05:49.515-04:00 DEBUG (0388-0764) <MessageFrameWorkDispatch> [wswc_http] Broker request brokerConnect FAILED, error: HTTP request to vcenter.fabrikam.com/broker/xml (vcenter.fabrikam.com) failed with a status code of 400, userError: An HTTP error occurred: status code = 400. 2013-06-21T17:05:49.515-04:00 ERROR (0388-0764) <MessageFrameWorkDispatch> [wswc_command] An HTTP error occurred: status code = 400.
Here's a snippet of my logs from a healthy connection for comparison:
2013-06-21T15:45:17.956-07:00 INFO (1330-1F80) <8064> [wswc] Log for VMware View Client, version=5.3.0 build-1042023 2013-06-21T15:45:17.956-07:00 INFO (1330-1F80) <8064> [wswc] hostname=HOST 2013-06-21T15:45:17.956-07:00 INFO (1330-2390) <9104> [MessageFrameWork] Program 'wswc - VMware View Client' started, version=5.3.0 build-1042023, pid=0x1330, buildtype=release, usethread=1, closeafterwrite=0 2013-06-21T15:45:17.976-07:00 INFO (1330-0690) <logloaded> [MessageFrameWork] Plugin 'wswc_command - VMware View Connection Server Command Handler' loaded, version=5.3.0 build-1042023, buildtype=release 2013-06-21T15:45:17.976-07:00 INFO (1330-1100) <logloaded> [MessageFrameWork] Plugin 'wswc_http - VMware View Client HTTP Handler' loaded, version=5.3.0 build-1042023, buildtype=release 2013-06-21T15:45:17.986-07:00 INFO (1330-1CF0) <logloaded> [MessageFrameWork] Plugin 'wswc_pcoip - VMware View Client PCoIP Interaction Handler' loaded, version=5.3.0 build-1042023, buildtype=release 2013-06-21T15:45:17.986-07:00 INFO (1330-16B4) <logloaded> [MessageFrameWork] Plugin 'wswc_rdp - VMware View RDP Handler' loaded, version=5.3.0 build-1042023, buildtype=release 2013-06-21T15:45:17.986-07:00 INFO (1330-2130) <logloaded> [MessageFrameWork] Plugin 'wswc_rsa - VMware View RSA Handler' loaded, version=5.3.0 build-1042023, buildtype=release 2013-06-21T15:45:17.986-07:00 INFO (1330-20C0) <logloaded> [MessageFrameWork] Plugin 'wswc_tunnel - VMware View Secure Tunnel Client' loaded, version=5.3.0 build-1042023, buildtype=release 2013-06-21T15:45:17.986-07:00 INFO (1330-22FC) <logloaded> [MessageFrameWork] Plugin 'wswc_ui - VMware View Client UI handler' loaded, version=5.3.0 build-1042023, buildtype=release 2013-06-21T15:45:17.996-07:00 INFO (1330-08F8) <logloaded> [MessageFrameWork] Plugin 'wssm_uimanager - VMware View Framework UI Host' loaded, version=5.3.0 build-1042023, buildtype=release 2013-06-21T15:45:17.996-07:00 INFO (1330-2394) <logloaded> [MessageFrameWork] Plugin 'ws_winauth - VMware View Framework Windows Authentication Support' loaded, version=5.3.0 build-1042023, buildtype=release 2013-06-21T15:45:18.006-07:00 INFO (1330-2390) <Main Thread> [wswc] Windows Client started 2013-06-21T15:45:20.646-07:00 INFO (1330-1EC8) <MessageFrameWorkDispatch> [wswc_tunnel] Data frame policy set to NEGOTIATE (proposing 0 bytes) 2013-06-21T15:45:20.646-07:00 INFO (1330-1EC8) <MessageFrameWorkDispatch> [wswc_tunnel] Received chunk window set to 2 2013-06-21T15:45:20.746-07:00 INFO (1330-0B38) <TunnelRead> [wswc_tunnel] Tunnel Unnamed: connected to server 'SERVER', start tunnel protocol 2013-06-21T15:45:20.756-07:00 INFO (1330-0B38) <TunnelRead> [wswc_tunnel] Tunnel Unnamed authenticated Ok, set state = running 2013-06-21T15:45:33.518-07:00 INFO (1330-19EC) <DesktopWindow> [wswc_ui] Ask UsbDeviceManager to open client/agent channel 2013-06-21T15:45:33.518-07:00 INFO (1330-19EC) <DesktopWindow> [wswc_ui] vmware-view-usbd channel created OK
Have you tried connecting with the "Do not verify server identity" checked under the SSL Setup? That might help rule out (or not) a certificate issue. Any events show up in View?
Just noticed that the server you're connecting to is "vcenter.fabrikam.com". You need to point the client to the Connection Server/Broker rather than vCenter (and potentially Composer). Is that server running your Connection Server as well (and thus on non-standard ports)?
We achieve this by setting up dedicated desktop pool with SSO off (as explained by mittim12) and configuring zero client to use kiosk mode using kiosk user. In this way users work in shift basis who migrated to new VDI did not see any difference as they directly enter their own user name and password to get their desktop. But in this way if the user logged in to different station he will not get his own desktop/profile.
Message was edited by: roshnet
Hi,
Has anyone implemented SIOC on VDI environment? We experienced some storage latency issues in our VDI due to some misbehaving VDs. We have not implemented SIOC as we haven't seen any recommendations/guides on this. Would like to hear their experience if anyone has done this.
Rgds
Hi All,
We are facing very strange issue in our new VD environment. We start receiving calls from different users regarding their VD Session Lost suddenly when they try to access Facebook from IE 8. This start happening at exactly 12.30pm as our proxy only allow FB access between 12.30 to 1.30. Has anyone experience this issue before or has any idea about this?
Your response is greatly appreciated.
Rgds
I tried a totally different machine (3rd machine.) It succeeded to connect and saw the pool.
But now I have another problem, which I'll post about in another thread.
Thanks !
I'm at another "stuck" point.
My linked clone pool refuses to finish. Here are my events from the relevent time period (most recent in first screenshot):
http://screencast.com/t/KJM6k67qTZ
Basically.. the events show the following:
1. Trying to provision.
2. Successfully configured video settings for Machine VM (three A-OK)
3. Provisioning error occured for (all three machines): Customization operation timed out.
4. Automatic error recover for Pool.
5. Attempting to restart (all three machines).
6. Automatic error recovery for pool: Delete all three machines.
7. Successful delete of all three machines.
8. Go to 2.
And repeat all night / day long.
In connecting to the ESXi server I find:
1. All three VMs are started.
2. They're waiting for someone to CTL-ALT-DEL them.
3. In spot checking, (and manually logging on)
they ARE getting DHCP (which I learned could be a cause of failure to provision; but this is not problem)
Any thoughts?
Attached my vCenter logs if that would help. Thanks !
