Search results

• ESX Script Extracts and Examples
  $EmailBody += "`n`n`nCheck started : " + (Get-Date $start -uFormat $DateFormat) + "`n" Getting BIOS, NIC and HBA driver versions is dependant on what's reported to the ES
  18 KB (2,044 words) - 15:34, 26 September 2016
• Getting Started (PowerCLI)
  [[Category:Getting Started]]
  8 KB (1,042 words) - 07:46, 27 September 2016
• Active Directory (PowerShell)
  == Getting Started ==
  10 KB (1,303 words) - 15:24, 28 August 2013
• Virtual Machine Script Extracts and Examples
  Log("Getting list of VMs to check...") Log "Getting resource pools..."
  31 KB (3,550 words) - 08:52, 19 October 2016
• Group Policy (Active Directory)
  = Getting Started =
  13 KB (1,783 words) - 15:28, 19 September 2013
• Troubleshooting (vCentre)
  * SQL tends to report itself as started, despite the fact that it hasn't made its database instances available yet.
  9 KB (1,479 words) - 13:32, 15 January 2013
• Virtual Infrastructure DB Project
  This started life as small script to collect VM info from 5 or 6 vCentre's (that were a
  10 KB (1,290 words) - 10:37, 19 December 2011
• Zimbra FOSS Full Backup
  echo "`date +%X` Stats started..." # SSS [not req] echo "$TYPE Backup started at: `date`"
  32 KB (4,445 words) - 09:52, 4 April 2012
• Virtual Machines
  ...blems as new machine behaves as if it was ungracefully shutdown when first started, but normally successful. Source machine needs to be relatively quiet. ...ete the UUID line (VMware will prompt to generate a new one when the VM is started).
  42 KB (6,803 words) - 13:32, 26 September 2016
• Windows 2008
  | 0x8004131E || SCHED_E_PAST_END_BOUNDARY || Task cannot be started after the trigger end boundary
  14 KB (2,016 words) - 11:52, 7 May 2019
• Ubuntu
  Logger "Started backup script..." ...ith two disks in RAID1 has failed, one disk has been replaced, and machine started again
  29 KB (4,446 words) - 15:21, 23 August 2016
• Procedures (Zimbra)
  #* Also copy off any existing local backup (so that a new full backup can be started following the upgrade)
  14 KB (2,241 words) - 08:02, 31 July 2013
• VI-DB db-base-data-v2.0.ps1
  Log "Started script run at $start" Log("Getting Lab Manager VM info...")
  17 KB (1,830 words) - 22:06, 25 October 2011
• VI-DB db-base-data-v2.1.ps1
  Log "Started script run at $start" Log("Getting Lab Manager VM info...")
  18 KB (1,879 words) - 08:50, 12 October 2011
• VI-DB db-base-data-v2.2.ps1
  Log "Started script run at $start" Log("Getting Lab Manager VM info...")
  18 KB (1,898 words) - 10:09, 19 December 2011
• VI-DB db-base-data-v2.3.ps1
  Log "Started script run at $start" Log("Getting Lab Manager VM info...")
  18 KB (1,908 words) - 10:09, 19 December 2011
• PowerShell Examples
  Log "Started script run at $start"
  18 KB (2,187 words) - 13:29, 18 April 2012
• MS SQL
  ...to, reboot the machine, then log back in and ensure all SQL services have started correctly
  17 KB (2,557 words) - 13:42, 22 September 2019
• High System Load (Ubuntu)
  | <code>g</code> || <code>TTY</code> || Controlling TTY || Device that started the process
  19 KB (2,322 words) - 20:59, 11 October 2012
• VI-DB db-base-data-v1.0.ps1
  Log "Started script run at $start" Log("Getting v3 LUN info...")
  32 KB (2,962 words) - 22:06, 25 October 2011
• Troubleshooting (Virtual Machine)
  ...on the VM. To commit a snapshot in a running VM, first a new snapshot is started, then the original redo files are merged with the base disk(s), then the ex
  20 KB (3,270 words) - 16:43, 23 August 2012
• Zimbra
  #* Also copy off any existing local backup (so that a new full backup can be started following the upgrade)
  21 KB (3,146 words) - 15:30, 1 May 2012
• VI-DB db-base-data-v1.1.ps1
  Log "Started script run at $start" Log("Getting v3 LUN info...")
  37 KB (3,560 words) - 22:06, 25 October 2011
• VI-DB db-base-data-sub-v2.0.ps1
  Log "Started sub-script run at $start" Log("Getting v3 LUN info...")
  36 KB (3,811 words) - 22:03, 25 October 2011
• VI-DB db-base-data-sub-v2.1.ps1
  Log "Started sub-script run at $start" Log("Getting v3 LUN info...")
  38 KB (3,968 words) - 22:04, 25 October 2011
• VI-DB db-base-data-sub-v2.2.ps1
  Log "Started sub-script run at $start" Log("Getting v3 LUN info...")
  38 KB (4,040 words) - 22:04, 25 October 2011
• VI-DB db-base-data-sub-v2.3.ps1
  Log "Started sub-script run at $start" Log("Getting v3 LUN info...")
  39 KB (4,084 words) - 22:07, 25 October 2011
• VI-DB db-base-data-v1.2.ps1
  Log "Started script run at $start" Log("Getting v3 LUN info...")
  45 KB (4,364 words) - 22:06, 25 October 2011
• VI-DB db-base-data-sub-v2.4.ps1
  Log "Started sub-script run at $start" Log("Getting v3 LUN info...")
  47 KB (4,859 words) - 22:07, 25 October 2011
• VI-DB db-base-data-v1.2.1.ps1
  Log "Started script run at $start" Log("Getting v3 LUN info...")
  45 KB (4,470 words) - 22:06, 25 October 2011
• VI-DB db-base-data-v1.2.2.ps1
  Log "Started script run at $start" Log("Getting v3 LUN info...")
  46 KB (4,545 words) - 22:06, 25 October 2011
• VI-DB db-base-data-sub-v2.5.ps1
  Log "Started sub-script run at $start" Log("Getting v3 LUN info...")
  48 KB (5,058 words) - 08:51, 12 October 2011
• VI-DB db-base-data-sub-v2.6.ps1
  Log "Started sub-script run at $start" Log("Getting v3 LUN info...")
  50 KB (5,286 words) - 10:08, 19 December 2011
• VI-DB db-base-data-sub-v2.7.ps1
  Log "Started sub-script run at $start" Log("Getting v3 LUN info...")
  57 KB (5,986 words) - 10:08, 19 December 2011
• VCP4
  ** A fail-over has occurred but FT network link down, so new secondary not started
  29 KB (4,248 words) - 21:56, 16 June 2013
• VI-DB db-base-data-sub-v2.8.ps1
  Log "Started sub-script run at $start" Log("Getting v3 LUN info...")
  60 KB (6,255 words) - 10:05, 19 December 2011
• VI-DB db-base-data-sub-v2.9.ps1
  Log "Started sub-script run at $start" Log ("Getting CLUSTERS....")
  63 KB (6,615 words) - 09:49, 19 December 2011

View (previous 100 | next 100) (20 | 50 | 100 | 250 | 500)