The benefits of this upgrade for the client are as follows:
·         Performance improvements in vCenter Server and vSphere Web Client http://www.vmware.com/files/pdf/techpaper/Whats-New-Perf-vSphere6.pdf
·         Better support of Microsoft Clustering (including vMotion of clustered VMs)http://kb.vmware.com/kb/1037959
·         Different security enhancements (host security, certificate management through centralized CA, etc.)https://www.vmware.com/files/pdf/vsphere/VMW-WP-vSPHR-Whats-New-6-0-PLTFRM.pdf
 
 
I would also highly recommend considering Enterprise Plus edition of vSphere for the client in the future, as it brings features that can further standardize and automate the system as follows:
·         Storage I/O control (SIOC) and IOPS reservationhttps://blogs.vmware.com/vsphere/2015/07/sioc-io-distribution-with-reservations-limits-part1.html
·         Cross-vCenter vMotion and Long Distance vMotionhttps://www.vmware.com/files/pdf/vsphere/VMW-WP-vSPHR-Whats-New-6-0-PLTFRM.pdf.
 
The process of upgrading to vSphere 6.0 consists of the following subsequent steps:
 
1.       Upgrading vCenter Server (3 days):
a.       Preparing vCenter 5.5 for upgrade
b.      Upgrading vSphere and vCenter licenses (requires access to the MyVMware portal)
c.       Migrating from SSO to PSC
d.      Upgrading vCenter
e.      Upgrading vSphere Update Manager
f.        Testing the new vCenter
 
2.       Installing ESXi on new hosts (3 days):
a.       Checking / configuring remote access to the servers (iLO)
b.      Updating firmware and BIOS to the latest versions
c.       Setting up the BIOS settings on the hosts
d.      Preparing image for auto-installation
e.      Performing installation
f.        Configuring the management network
 
3.       Configuring the hosts (2 days):
a.       Configuring networking on the hosts (best practices!)
b.      Configuring hosts for storage and attaching datastores (best practices!)
c.       Migrating VMs
 
4.       Upgrading VMs (work time depends on the company’s policy for the planned system outages):
a.       Scheduling VMware Tools upgrade
b.      Scheduling VM hardware upgrade
c.       Optimizing VMs according to the running applications and the best practices.
VN:F [1.9.22_1171]
Rating: 10.0/10 (1 vote cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Get-Content -Path “C:\Logs*” | Select-String -Pattern “nameofthingtofind”

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently we had a task to update all the Finished folders in Olympus to remove old items old than 2 months. I tried to use the Group function of this software to deploy the settings however they weren’t taking. Instead of editing the individual users I wrote the following powershell to Edit each users XML configuration

$Files = Get-ChildItem \folderlocation
ForEach($file in $files) {
$xml = [pastacode provider="manual" lang="markup" manual=""](Get-Content $file.FullName)
$xml2 = $xml.Profile.TranscriptionInformation.FolderDesign.FolderList.Folder | Where-Object { $_.parent -eq '101' -and $_.type -eq '115'}
$xml2.Actions.Cleaning.fixed = [io.path]::GetFileNameWithoutExtension($file.Name)
$xml2.Actions.Cleaning.Enabled = '1'
$xml2.Actions.Cleaning.Period = '2'
$xml2.Actions.Cleaning.Unit = '1'
$xml2.Actions.Cleaning.Option = '2'
$xml.Save($file.FullName)
}
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

2014-06-17_16h26_59[1]Recently during a Veeam backup HA kicked in due to a problem with VCenter and marked two machines as Invalid

  •  Veeam started backup and created snapshot on affected VMs
  • HA kicked in after VCenter Server failure
  • Vcenter tried to move the machines after the HA event but they were locked by the snapshot Veeam had (the hypervisor has a lock because of the snapshot)
  • Machine couldn’t move but Vmware removed them from inventory and tried to register them to another host, without success
  • Machines marked as Invalid, Removing machines from Inventory and registering the machines manually did not work
  • The machines are locked however still powered on and response

Fix to get VM’s registered on VCenter

  • Stop any tasks (i.e. Veeam) that might trigger a snapshot on affected machines
  • Temporarily disable DRS in the cluster (when we power up the machine we don’t want Vsphere to power it up on another host otherwise the lock will persists)
  • Power affected VMs off gracefully from within the OS.
  • Login to vcenter and select Host which failed and . Unregister “unkown” VM’s listed (these should be the actual Vms). Unregistering should remove the lock.
  • Register the virtual machines using the vmx files in the datastore
  • Check no snapshots are present, if yes delete or consolidate
  • Power on Vm
  • Re-enable DRS
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

This Exports a report of emails and also a copy of all the emails to a mailbox ( Disovery ) you can do this via the Web Based Gui : https://youwebmaildomain/ecp/?rfr=owa with the right user permissions

New-MailboxSearch -Name "WeekendOutage-Search" -StartDate "1/1/2009" -EndDate "12/31/2009" -SourceMailboxes "Amit Tank" -TargetMailbox "Discovery Search Mailbox" -SearchQuery '"Weekend" and "Outage"' -MessageTypes Email -IncludeUnsearchableItems -LogLevel Full

But you cannot exclude emails from specific domains from this discovery search .e.g only sent from Externally. You can exclude Generic Keywords using NOT in the -SearchQuery but its generic to the email like the search Query above.

The New-MailboxExportRequest Should be able to do this but it doesn’t , just exports everything probably because the operator is too specific and doesn’t suport -notlike 🙁

New-MailboxExportRequest -Mailbox "Discovery Search Mailbox" -contentfiler{sender -ne "*@internaldomain.com"} -Filepath \\samba\share\withexchangepermissions\file.pst

But we can actually just delete all the Internal Mail using Search Mailbox

 

Search-Mailbox -Identity "Discovery Search Mailbox" -searchquery 'From:"@internaldomain.com"' -DeleteContent

Now we can just export this to a PST

New-MailboxExportRequest -Mailbox "Discovery Search Mailbox" -Filepath \\samba\share\withexchangepermissions\file.pst
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

owncloudNB : Are you running a 32bit OS?

 

cat /etc/0s-release

If Pretty_Name = i586 it means you are, means your file size can only be 2Gigabytes which means you can only set your max filesizes below to 2000M (any more and you will get Unable to set upload directory)

Php.ini ( timeouts )

vi /etc/php5/apache5/php.ini

post_max_size = 2000M

upload-max-filesize = 2000M

max_execution_time = 300  

Increase File Upload Size
Go to /srv/www/htdocs/owncloud/ and edit .user.ini and  the .htaccess

upload_max_filesize=2000M
post_max_size=2000M

Restart Apache

systemctl restart apache2.service


Installed from
 
https://susestudio.com/a/TadMax/owncloud-in-a-box
 
SSL
Install SSL ; http://www.unixmen.com/create-ssl-cetificates-in-opensuse-12-3/
Digicert Tool – https://www.digicert.com/easy-csr/openssl.htm
 
Install Multiple SSL’s – https://www.digicert.com/ssl-support/apache-multiple-ssl-certificates-using-sni.htm
 
Disk Useage
df -h
 
SSL Cert Locations
/etc/apache2/ssl.key/
 
Access Logs
/var/log/apache2
 
Error Logs
 /var/log/apache2
 
Apache Files
/srv/www/htdocs/owncloud
 
Php.ini ( timeouts ) ***NB*** Its a 32bit machine can only upload 2 Gigs
/etc/php5/apache5
 
max_execution_time = 300
 
Apache Running as user wwwrun
 
Increase File Upload Size
 
Go to /srv/www/htdocs/owncloud/ and edit .user.ini and  the .htaccess

upload_max_filesize=2000M
post_max_size=2000M
 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

SQL

Shows all the databases of a server and the last time they were accessed

SELECT DatabaseName, MAX(LastAccessDate) LastAccessDate
FROM
    (SELECT
        DB_NAME(database_id) DatabaseName
        , last_user_seek
        , last_user_scan
        , last_user_lookup
        , last_user_update
    FROM sys.dm_db_index_usage_stats) AS PivotTable
UNPIVOT 
    (LastAccessDate FOR last_user_access IN
        (last_user_seek
        , last_user_scan
        , last_user_lookup
        , last_user_update)
    ) AS UnpivotTable
GROUP BY DatabaseName
HAVING DatabaseName NOT IN ('master', 'tempdb', 'model', 'msdb')
ORDER BY 2

Shows all the current database connections currently

SELECT @@ServerName AS server,NAME AS dbname,COUNT(STATUS) AS number_of_connections,GETDATE() AS timestampFROM sys.DATABASES sdLEFT JOIN sysprocesses sp ON sd.database_id = sp.dbidWHERE database_id NOT BETWEEN 1 AND 4GROUP BY NAMEORDER BY 3 


VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

worksiteWhen renaming a user in iManage/ Worksite the logs show

“[Microsoft][ODBC SQL Server Driver][SQL Server]A cursor with the name ‘Store’ already exists

The trigger in the DOCMASTER Table contains a cursor called Store which conflicts with the stored procedure. Choose modify on the trigger and do a search and replace Store another variable e.g. StoreTrigger. Execute the trigger after to save and try again

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

In Exchange EWS when trying to delete an item you get the following error : cannot find an overload for “delete” and the argument count 0 using

$item.Delete()

 

You need to give it a an enumeration e.g.

They can be found here : http://msdn.microsoft.com/en-us/library/microsoft.exchange.webservices.data.deletemode(v=exchg.80).aspx

$item.Delete([Microsoft.Exchange.WebServices.Data.DeleteMode]::HardDelete)

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Repeater8540_FrontWtop_HR_512Upgrading a Citrix branch repeater ( Now called CloudBridge)  to the latest firmware requires the License currently installed to be in date and under maintenance. If you renew your Citrix Maintenance you need to re-download all your licenses and reupload them to the branch repeater before it accepts the new firmware file.

Upon reuploading one of the new License file to a branch repeater I was given the error

Add License failed: The license is not an upgrade license which is required since a base license is already installed

This required me to delete the current license from the Citrix Branch Repeater ( Warning this will disconnect accelerated connections so make sure you do this out of production hours ) and reupload the license.

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)