5 Kasım 2015 Perşembe

Using PsInfo

Using PsInfo

By default PsInfo shows information for the local system. Specify a remote computer name to obtain information from the remote system. Since PsInforelies on remote Registry access to obtain its data, the remote system must be running the Remote Registry service and the account from which you runPsInfo must have access to the HKLM\System portion of the remote Registry.
In order to aid in automated Service Pack updates, PsInfo returns as a value the Service Pack number of system (e.g. 0 for no service pack, 1 for SP 1, etc).
Usage: psinfo [[\\computer[,computer[,..] | @file [-u user
[-p psswd]]] [-h] [-s] [-d] [-c [-t delimiter]] [filter]
\\computerPerform the command on the remote computer or computers specified. If you omit the computer name the command runs on the local system, and if you specify a wildcard (\\*), the command runs on all computers in the current domain.
@fileRun the command on each computer listed in the text file specified.
-uSpecifies optional user name for login to remote computer.
-pSpecifies optional password for user name. If you omit this you will be prompted to enter a hidden password.
-hShow list of installed hotfixes.
-sShow list of installed applications.
-dShow disk volume information.
-cPrint in CSV format.
-tThe default delimiter for the -c option is a comma, but can be overriden with the specified character.
filterPsinfo will only show data for the field matching the filter. e.g. "psinfo service" lists only the service pack field.

Example Output

c:> psinfo \\development -h -d

PsInfo v1.6 - local and remote system information viewer
Copyright (C) 2001-2004 Mark Russinovich
Sysinternals - www.sysinternals.com

    System information for \\DEVELOPMENT:
    Uptime: 28 days, 0 hours, 15 minutes, 12 seconds
    Kernel version: Microsoft Windows XP, Multiprocessor Free
    Product type Professional
    Product version: 5.1
    Service pack: 0
    Kernel build number: 2600
    Registered organization: Sysinternals
    Registered owner: Mark Russinovich
    Install date: 1/2/2002, 5:29:21 PM
    Activation status: Activated
    IE version: 6.0000
    System root: C:\WINDOWS
    Processors: 2
    Processor speed: 1.0 GHz
    Processor type: Intel Pentium III
    Physical memory: 1024 MB
    Volume Type Format Label Size Free Free
    A: Removable 0%
    C: Fixed NTFS WINXP 7.8 GB 1.3 GB 16%
    D: Fixed NTFS DEV 10.7 GB 809.7 MB 7%
    E: Fixed NTFS SRC 4.5 GB 1.8 GB 41%
    F: Fixed NTFS MSDN 2.4 GB 587.5 MB 24%
    G: Fixed NTFS GAMES 8.0 GB 1.0 GB 13%
    H: CD-ROM CDFS JEDIOUTCAST 633.6 MB 0%
    I: CD-ROM 0% Q: Remote 0%
    T: Fixed NTFS Test 502.0 MB 496.7 MB 99%
    OS Hot Fix Installed
    Q147222 1/2/2002
    Q309521 1/4/2002
    Q311889 1/4/2002
    Q313484 1/4/2002
    Q314147 3/6/2002
    Q314862 3/13/2002
    Q315000 1/8/2002
    Q315403 3/13/2002
    Q317277 3/20/2002


4 Kasım 2015 Çarşamba

VMware ESXi 6.0 host fails to detect local disk after patching or applying Update 1 on HP Proliant Gen 9 servers (2120539)

VMware ESXi 6.0 host fails to detect local disk after patching or applying Update 1 on HP Proliant Gen 9 servers (2120539)
Symptoms
After applying patches VMware ESXi 6.0, Patch Release ESXi600-201504001, VMware ESXi 6.0, Patch Release ESXi600-201505001, VMware ESXi 6.0, Patch Release ESXi600-201507001, and VMware ESXi 6.0 Update 1 on an HP Proliant Gen 9 servers with an HP ESXi 6.0 custom image, you experience these symptoms:

·   The ESXi 6.0 host fails to boot
·   The ESXi 6.0 host fails to detect the local disk
Cause
This issue occurs because the existing scsi-hpsa driver that was included in the HP custom image was replaced by the scsi-hpsa driver that are included in the ESXi 6.0 patches and Update 1.

Resolution
This is a known issue affecting HP Proliant G9 servers that have been deployed with an HP ESXi 6.0 custom image.

Currently, there is no resolution.

To work around this issue, you must back out the patches by reverting to the previous state of the host, then reapply the patches in such a way as to update all but the 
scsi-hpsa driver. For more information about reverting to a previous state of an ESXi host, see Reverting to a previous version of ESXi (1033604).

After successfully reverting to the previous state of the ESXi host, re-apply the patches:

To re-apply ESXi600-201504001 and ESXi600-201505001:
1. Log in to the ESXi host through SSH as the root user
2. Run this command on each of patches ESXi600-201504001 and ESXi600-201505001:

esxcli software vib update -n esx-base -d /path/ESXi600-20150xxxx.zip

where xxxx equals 4001 and 5001, successively.
To re-apply ESXi600-201507001:
1. Log in to the ESXi host through SSH as the root user.
2. Run this command:

esxcli software vib update -n esx-base -d /path/ESXi600-201507001.zip
esxcli software vib update -n tools-light -d /path/ESXi600-201507001.zip


These are driver related vibs. Apply these vibs according to your system environment.

esxcli software vib update -n misc-drivers -d /path/ESXi600-201507001.zip
esxcli software vib update -n scsi-bnx2i -d /path/ESXi600-201507001.zip
esxcli software vib update -n sata-ahci -d /path/ESXi600-201507001.zip
esxcli software vib update -n lsu-lsi-lsi-mr3-plugin -d /path/ESXi600-201507001.zip
esxcli software vib update -n lsu-lsi-megaraid-sas-plugin -d /path/ESXi600-201507001.zip

Note: These commands do not update the 
scsi-hpsa driver.
Additional Information
For more information, see HP Advisory VMware - No VMware vSphere 6.0 Inbox Support for HP Smart Array Controllers or Smart Host Bus Adapters.

Note: The preceding link was correct as of August 11, 2015. If you find the link is broken, please provide feedback and a VMware employee will update the link.

To be alerted when this article is updated, click Subscribe to Document in the Actions box. 





26 Ekim 2015 Pazartesi

IBM Storwize V7000 disk firmware upgrade test

IBM Storwize V7000 disk firmware upgrade test


pscp.exe ile diğer firmware ve upgrade test dosyları aynı klasör içerisinde bulunmalı

upgrade test uygulmasını storvize içerisine almak için aşağıdaki komutları kullanıyoruz.

pscp.exe IBM2076_INSTALL_upgradetest_15.15 superuser@10.10.10.45:/home/admin/upgrade

superuser@10.10.10.45's password:

IBM2076_INSTALL_upgradete | 66 kB |  66.8 kB/s | ETA: 00:00:00 | 100%

Disk firmware dosyamızı benzeri şekilde storwize içerisine alıyoruz.

pscp.exe IBM2076_DRIVE_20150619  superuser@10.10.10.45:/home/admin/upgrade

superuser@10.10.10.45's password:

IBM2076_DRIVE_20150619    | 51860 kB | 25930.3 kB/s | ETA: 00:00:00 | 100%

------------------------------------------------------------------------------

Storwize V7000 üzerinden aşağıdaki komutları çalıştırıyoruz.

login as: superuser
superuser@10.10.10.45's password:
IBM_Storwize:Storwize7000:superuser>

Upgrade uygulamasını aktif etmek için aşağıdaki komutu kullanıyoruz.
IBM_Storwize:Storwize7000:superuser>svctask applysoftware -file
IBM2076_INSTALL_upgradetest_15.15

CMMVC6227I The package installed successfully.


Upgrade test işlemine başlamak için svcupgradetest komutunu kullanıyoruz.

IBM_Storwize:Storwize7000:superuser>svcupgradetest -f -d

svcupgradetest version 15.15

Please wait, the test may take several minutes to complete.


******************* Warning found *******************

This tool has found the internal disks of this system are
not running the recommended firmware versions.
Details follow:

+----------------------+-----------+------------+------------------------------------------+
| Model                | Latest FW | Current FW | Drive Info                               |
+----------------------+-----------+------------+------------------------------------------+
| ST9300653SS          | B63M      | B63L       | Drive   23 in slot 10 in enclosure  2    |
|                      |           |            | Drive   24 in slot 14 in enclosure  2    |
|                      |           |            | Drive   25 in slot 23 in enclosure  2    |
|                      |           |            | Drive   26 in slot 20 in enclosure  2    |
|                      |           |            | Drive   27 in slot 15 in enclosure  2    |
|                      |           |            | Drive   28 in slot 16 in enclosure  2    |
|                      |           |            | Drive   29 in slot 22 in enclosure  2    |
|                      |           |            | Drive   30 in slot 24 in enclosure  2    |
| ST900MM0006          | B56S      | B56N       | Drive  230 in slot 17 in enclosure  7    |
|                      |           |            | Drive  231 in slot 18 in enclosure  7    |
|                      |           |            | Drive  232 in slot 19 in enclosure  7    |
|                      |           |            | Drive  233 in slot 20 in enclosure  7    |
|                      |           |            | Drive  235 in slot 22 in enclosure  7    |
|                      |           |            | Drive  236 in slot 23 in enclosure  7    |
|                      |           |            | Drive  237 in slot 24 in enclosure  7    |
|                      |           |            | Drive  238 in slot 24 in enclosure  1    |
|                      |           |            | Drive  239 in slot 23 in enclosure  5    |
|                      |           |            | Drive  240 in slot 21 in enclosure  7    |
+----------------------+-----------+------------+------------------------------------------+

We recommend that you upgrade the drive microcode at an
appropriate time. If you believe you are running the latest
version of microcode, then check for a later version of this tool.
You do not need to upgrade the drive firmware before starting the
software upgrade.

Results of running svcupgradetest:
==================================

The tool has found 0 errors and 1 warnings.

IBM_Storwize:Storwize7000:superuser>

20 Ekim 2015 Salı

How to Shadow a Terminal Server Session Without Prompt for Approval

How to Shadow a Terminal Server Session Without Prompt for Approval



Shadow Error "The oprerator or administrator has refused the request"

If you would like to shadow the Terminal Server sessionand you do not want to be prompted for permission, set the local Group Policy on the server that is running Terminal Services.


To remote control the console with no prompt for approval:

  1. Open Group Policy Editor (Gpedit.msc) on the server that is running Terminal services.
  2. Under Computer Configuration, expand Administrative templates, expand Windows Components, and then click Remote Desktop Services, and then click Remote Desktop Session Host, Connections.
  3. Right-click Sets rules for remote control of Remore Desktop Service user sessions, and then clickProperties.
  4. Select the Enabled option.
  5. Under Options, click Full Control without user's permission.

Installation of component VCSServiceManager failed with error code '1603

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2113068


Cause

This issue occurs when the vCenter Servers Data Source Name (DSN) has a trailing space at the end of its name.

Resolution

This is a known issue affecting vCenter Server 6.0.

To resolve this issue, edit and rename the vCenter Server's DSN and remove the trailing space.

To edit and rename the vCenter Server's DSN and remove the trailing space:
  1. Log in to the vCenter Server as an administrator.
  2. Click Start > Control Panel > Administrative Tools > Data Sources (ODBC).
  3. Click the System DSN tab.
  4. In System Data Sources, select the Data Source that vCenter Server is using, as noted in the previous section of this article.
  5. Click Configure.
  6. In the Configure pane, you see the name of the configured database server in the server text box. Update the DSN to remove the trailing white space.
  7. Click Next.
  8. Enter the appropriate log in credentials on the next page.

    Note: The log in information here is not saved, it is simply used for the configuration and testing of the Data Source.
  9. Complete the wizard and run the installation again.

Raporları oluşturmak için Flex üzerindeki master server'a PuTTY üzerinden appadmin ile giriş yapın ve "sudo -i" ile root kulla...