In dem File /var/log/vmkernel.log sind schon Einträge, aber nicht unmittelbar nachdem ich vmkfstools -V sondern schon ältere: Mount Point Volume Name UUID Mounted Type Size Free Hier die Ausgabe von esxcli storage filesystem esxcli storage filesystem list Das habe ich ursprünglich nicht ausgeführt, da dort stand, dass das nicht für lokale Platten ist. Maybe try asking in PowerCli sub-community and/or moving this question there would be a good call.Īchso, das meintest du. if all gone after stopping the service then starting the service should be fine, but if they are not killed then you have a problem and "/etc/init.d/vsanmgmtd status" will still say 'running' but that daemon may be hung and non-responsive. #ps | grep and/or note the process IDs, then stop the service and again check ps for the process IDs etc. etc/init.d/vsanmgmtd restart).Īdditionally, based on my experience troubleshooting vSAN/ESXi (for 3+ years professionally) I would always advise (if possible) integrating some form of basic checks as to whether the service was successfully stopped before being restarted or are you just dumping more non-functional processes on top of the hung ones e.g. If the users log onto other ordinary computers and use a View client, they have no problems with USB devices.ĭoes anyone in the community know how to pick apart an AD account profile that has been used with View in order to try and locate the offending piece of information?įrom my previous experiences with attempting similar (for fun/education) and LucD corroboration in posts such as this PowerCli Script to restart vSAN mgmt and vpd services on all ESXi in VC - unfortunately this isn't in the plain realm of 'Get-VMHostService' PowerCli calls and thus you would likely need something that would SSH to each host and run the commands locally (e.g. Also of note, it is only USB devices on the Samsung NCxxx device. Unfortunately in this situation that is not desirable, as we do not want to interrupt the users access to their network stored content. One might think problem solved, recreate the user's AD account. The USB detection problem occurred straight away. I have copied one of the user's AD account profiles and used it as a base for a new test user. It seems that there is some bad information being stored in the user's AD account profile. If I, or most other users for that matter, log in on the same Samsung NCxxx device, we experience none of these USB detection failures. Here is the confusing, annoying, FRUSTRATING part. We have a couple of other users who are not able use USB RFID readers. We think the issue is USB in general and not specifically storage devices. The USB storage devices appear to not be detected and the file systems do not mount. We have 2 users (confirmed) who cannot access USB storage devices when they are logged in. We are battling the following frustrating scenario. On the remote site most users use Samsung NCxxx devices. We have a satellite campus where we provide access to staff and students using VMware infrastructure, in this case Horizon View 7.5. I am one of the Sys Admins for an educational institution - Avondale College of Higher Education.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |