if you have sql logins that are based on AD users and the AD username changes at some point, these changes are not updated automatically in ms sql. i’ve read various posts that claim that restarting the sql service or the server entirely will cause the sql login info to update. i have yet to […]
haven’t been on 5.1 too long and i’m already looking into moving to 5.5. i’m motivated by the fact that there are some critical shortcomings (some new, some longstanding) that are addressed in 5.5. in addition, 5.1 seems to be a somewhat buggy release. i’ve been reading through various kb articles and the install guide […]
this will be my last post concerning VDR. recently, experienced an issue where i could no longer connect to the appliance via the VDR plugin. i tried a couple of things…restarting the VDR service on the appliance, restarting the appliance, and even uninstalling/reinstalling the VDR plugin. none of the above worked. eventually found an article […]
recently, we needed unity connection to attempt a transfer to an extension in the UCCX partition. first in unity we created a mailbox for the extension and set the greetings to play no recording and simply attempt transfer to this mailbox user’s extension. then in UCM under Advanced Features->Voice Mail->Cisco Voice Mail Port, we examined […]
i was able to deploy the VDP appliance after upgrading the majority of the ESX(i) hosts to 5.1. ESX 4.1 hosts are supported, but to deploy the 2TB version of VDP you need a datastore that’s actually a little over 3TB in size. the ability to create datastores >2TB debuts with ESXi 5.1. after deploying […]
(or password) this was a new one for me. after some problems involving the vcenter server a particular host was issuing this error. according to the vmware kb (proof: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2014275) and various blogs the easiest solution is to disconnect and reconnect the host to vcenter. unfortunately, after disconnecting the host i could not reconnect the host […]
vcenter rarely causes me problems (except during the 5.1 upgrade), it usually just runs and reboots are a non-issue. last week i rebooted the vcenter server to install windows updates and to fix something messed up with the VUM service. after the reboot, i was experiencing two issues. one was that i couldn’t connect to […]
files related to snapshots… .vmsn file = snapshot state/”the snapshot file” (will also contain VM memory data if included in snapshot) 00000#-delta.vmdk = delta disk 00000#.vmdk = descriptor file for delta disk (plain text) .vmsd = snapshot list (plain text) additional info: http://www.vmware.com/support/ws55/doc/ws_learning_files_in_a_vm.html and the video “vsphere-anatomy-of-snapshots”
in case there was ever a legal reason why an admin would need to access the contents of another user’s mailbox, the following specifies how to… http://help.outlook.com/140/gg709759.aspx (i’ve never tested this)
in exchange 2007 from the management console – “Server Configuration”. in this case it was version 8.3 enterprise and 8.3 means 2007 sp3. more info here: http://support.microsoft.com/kb/152439/en-us