Tuesday, December 9, 2008
Tuesday, December 2, 2008
Wednesday, November 26, 2008
Thursday, October 30, 2008
VMware Enhanced VMotion Compatibility (EVC)
http://www.vmware.com/files/pdf/vmotion_info_guide.pdf
VMware Enhanced VMotion Compatibility (EVC)—available in VMware Infrastructure 3 beginning with
version 3.5 Update 2—facilitates VMotion between different CPU generations, taking advantage of Intel Flex
Migration and AMD‐V Extended Migration technologies. When enabled for a cluster, EVC ensures that all
CPUs within the cluster are VMotion compatible. CPUs starting with Intel 45nm Core 2 (Penryn) and AMD
Second Generation Opteron (revision E or F) incorporate FlexMigration and Extended Migration technologies,
respectively.
The EVC feature allows the virtualization layer to mask or hide certain features by modifying the semantics
of the CPUID instruction and hides certain CPUID feature bits, even from nonprivileged code. For example,
with support from hardware, the virtualization layer modifies the semantics of the CPUID instruction to mask
or hide the SSE4.1 feature from any code (privileged or nonprivileged) to make CPUs differing in this feature
compatible for VMotion. Specifics on CPU compatibility with the Enhanced VMotion Compatibility feature
are available in the Basic System Administration guide for each ESX release starting with version 3.5 Update 2.
VMware Enhanced VMotion Compatibility (EVC)—available in VMware Infrastructure 3 beginning with
version 3.5 Update 2—facilitates VMotion between different CPU generations, taking advantage of Intel Flex
Migration and AMD‐V Extended Migration technologies. When enabled for a cluster, EVC ensures that all
CPUs within the cluster are VMotion compatible. CPUs starting with Intel 45nm Core 2 (Penryn) and AMD
Second Generation Opteron (revision E or F) incorporate FlexMigration and Extended Migration technologies,
respectively.
The EVC feature allows the virtualization layer to mask or hide certain features by modifying the semantics
of the CPUID instruction and hides certain CPUID feature bits, even from nonprivileged code. For example,
with support from hardware, the virtualization layer modifies the semantics of the CPUID instruction to mask
or hide the SSE4.1 feature from any code (privileged or nonprivileged) to make CPUs differing in this feature
compatible for VMotion. Specifics on CPU compatibility with the Enhanced VMotion Compatibility feature
are available in the Basic System Administration guide for each ESX release starting with version 3.5 Update 2.
Friday, October 24, 2008
Monday, October 20, 2008
Sunday, October 19, 2008
Thursday, September 25, 2008
Wednesday, September 24, 2008
Wednesday, September 17, 2008
Thursday, September 11, 2008
Friday, August 29, 2008
Thursday, August 28, 2008
Tuesday, August 26, 2008
Thursday, August 21, 2008
Monday, August 18, 2008
Monday, July 21, 2008
config_options_2300.pdf
http://www.ncsa.uiuc.edu/~aloftus/FibreChannel/Qlogic/config_options_2300.pdf
Execution Throttle. This setting specifies the maximum number of commands
executing on any one port. When a port’s execution throttle is reached, no new
commands are executed until the current command finishes executing. The valid
options for this setting are 1–256. The default is 16.
>4GByte Addressing. This option should be Enabled if the system has more
than 4 GB of memory available. The default is Disabled.
Execution Throttle. This setting specifies the maximum number of commands
executing on any one port. When a port’s execution throttle is reached, no new
commands are executed until the current command finishes executing. The valid
options for this setting are 1–256. The default is 16.
>4GByte Addressing. This option should be Enabled if the system has more
than 4 GB of memory available. The default is Disabled.
Sunday, July 20, 2008
Friday, July 18, 2008
Tuesday, July 15, 2008
Friday, July 11, 2008
Wednesday, July 9, 2008
Tuesday, July 8, 2008
SQL Table Ownership Changes, Quick and Easy - Scott Forsyth's Blog
SQL Table Ownership Changes, Quick and Easy - Scott Forsyth's Blog: "DECLARE @old sysname, @new sysname, @sql varchar(1000)
SELECT
@old = 'oldOwner_CHANGE_THIS'
, @new = 'dbo'
, @sql = '
IF EXISTS (SELECT NULL FROM INFORMATION_SCHEMA.TABLES
WHERE
QUOTENAME(TABLE_SCHEMA)+''.''+QUOTENAME(TABLE_NAME) = ''?''
AND TABLE_SCHEMA = ''' + @old + '''
)
EXECUTE sp_changeobjectowner ''?'', ''' + @new + ''''
EXECUTE sp_MSforeachtable @sql"
SELECT
@old = 'oldOwner_CHANGE_THIS'
, @new = 'dbo'
, @sql = '
IF EXISTS (SELECT NULL FROM INFORMATION_SCHEMA.TABLES
WHERE
QUOTENAME(TABLE_SCHEMA)+''.''+QUOTENAME(TABLE_NAME) = ''?''
AND TABLE_SCHEMA = ''' + @old + '''
)
EXECUTE sp_changeobjectowner ''?'', ''' + @new + ''''
EXECUTE sp_MSforeachtable @sql"
Monday, July 7, 2008
Sunday, July 6, 2008
Wednesday, July 2, 2008
Tuesday, July 1, 2008
Monday, June 23, 2008
Thursday, June 19, 2008
Wednesday, June 18, 2008
vmprofessional - esx scripted install
vmprofessional: "Partitioning is mostly a personal preference and everyone does it slightly differently. Here is my reasoning for setting up the partition table as it is displayed above:"
Tuesday, June 17, 2008
Thursday, May 29, 2008
Tuesday, May 27, 2008
Sunday, May 11, 2008
Sunday, May 4, 2008
RTFM Education » Blog Archive » VCB - Backup all running VMs
RTFM Education » Blog Archive » VCB - Backup all running VMs: "As student on my course last week gave me a little one line batch file that will backup every running VM on VC. This is it here:
for /f “tokens=2 delims=:” %%i in (’vcbvmname -h virtualcenter.rtfm-ed.co.uk -u administrator -p password -s Powerstate:on ^| find “name:”‘) do @rd /s /q “D:\Backups\All\%%i” &vcbmounter -h virtualcenter.rtfm-ed.co.uk -u administrator -p password -a name:”%%i” -r “D:\Backups\All\%%i” -t fullvm > “D:\Backups\All\%%i.log”
This use the vcbvmname command to search for just the VMs that currently powered on. It then pipes that information to the vcbMounter command to start a FullVM style backup. The progress of each backup is recorded in the LOG files for each VM."
for /f “tokens=2 delims=:” %%i in (’vcbvmname -h virtualcenter.rtfm-ed.co.uk -u administrator -p password -s Powerstate:on ^| find “name:”‘) do @rd /s /q “D:\Backups\All\%%i” &vcbmounter -h virtualcenter.rtfm-ed.co.uk -u administrator -p password -a name:”%%i” -r “D:\Backups\All\%%i” -t fullvm > “D:\Backups\All\%%i.log”
This use the vcbvmname command to search for just the VMs that currently powered on. It then pipes that information to the vcbMounter command to start a FullVM style backup. The progress of each backup is recorded in the LOG files for each VM."
Friday, May 2, 2008
Thursday, May 1, 2008
Wednesday, April 30, 2008
VDM - Setting an Externally Resolvable Name on a Connection Server
http://www.vmware.com/pdf/vdm20_manual.pdf
Setting an Externally Resolvable Name on a Connection Server
If VDM clients cannot directly access a VDM Connection Server by using
https:// where is the hostname of the VDM Connection Server,
you must specify an externally resolvable name for the VDM Connection Server. If the
VDM Connection Server is accessed from the Internet, set the name to something that
resolves on the Internet. This name can be something like
https://vdmservername.mycompany.com. Whenever this situation arises, you must set
the name for each VDM Connection Server that is unresolvable.
The process of setting the name is not the same for all installation types. For standard
or replica installations, you can set the name by using the Administrator user interface.
For a security server installation, you must edit or create a file with the settings and save
it on the security server.
To set the name on a standard or replica installation
1 On the Configuration page, in VDM Servers, select the VDM Connection Server to
set the name for.
2 Click Edit.
3 Enter the name in the External URL field.
4 Click OK.
5 Restart the VDM Connection Server service so that the changes take effect. Click
Start>Administrative Tools>Services and select the VMware VDM Connection
Server from the list of services. If the service is running, click Restart the service.
If the service is not running, click Start the service.
VMware, Inc. 41
Chapter 3 Installing and Configuring VDM
To set the name on a security server installation
1 Create or edit the properties file (locked.properties) so that it contains entries for
the externally resolvable name of the security server, the port number and the
client protocol.
The properties file is a text file. If it already exists, it is located at C:\Program
Files\VMware\VMware VDM\Server\sslgateway\conf\locked.properties.
always save this file in the same place, whether it already exists or not.
As an example, if the security server’s externally resolvable name is
vdmservername.mycompany.com, the port number is 443, and the client protocol
is https, you use a text editor to edit or create the properties file with the following
entries:
clientHost=vdmservername.mycompany.com
clientPort=443
clientProtocol=https
If a properties file already exists containing entries with these key words, replace
the entries with new entries from this list.
2 Save the file.
3 Restart the VDM Security Server service so that the changes take effect. Click
Start>Administrative Tools>Services and select the VMware VDM Security
Server from the list of services. If the service is running, click Restart the service.
If the service is not running, click Start the service.
Setting an Externally Resolvable Name on a Connection Server
If VDM clients cannot directly access a VDM Connection Server by using
https://
you must specify an externally resolvable name for the VDM Connection Server. If the
VDM Connection Server is accessed from the Internet, set the name to something that
resolves on the Internet. This name can be something like
https://vdmservername.mycompany.com. Whenever this situation arises, you must set
the name for each VDM Connection Server that is unresolvable.
The process of setting the name is not the same for all installation types. For standard
or replica installations, you can set the name by using the Administrator user interface.
For a security server installation, you must edit or create a file with the settings and save
it on the security server.
To set the name on a standard or replica installation
1 On the Configuration page, in VDM Servers, select the VDM Connection Server to
set the name for.
2 Click Edit.
3 Enter the name in the External URL field.
4 Click OK.
5 Restart the VDM Connection Server service so that the changes take effect. Click
Start>Administrative Tools>Services and select the VMware VDM Connection
Server from the list of services. If the service is running, click Restart the service.
If the service is not running, click Start the service.
VMware, Inc. 41
Chapter 3 Installing and Configuring VDM
To set the name on a security server installation
1 Create or edit the properties file (locked.properties) so that it contains entries for
the externally resolvable name of the security server, the port number and the
client protocol.
The properties file is a text file. If it already exists, it is located at C:\Program
Files\VMware\VMware VDM\Server\sslgateway\conf\locked.properties.
always save this file in the same place, whether it already exists or not.
As an example, if the security server’s externally resolvable name is
vdmservername.mycompany.com, the port number is 443, and the client protocol
is https, you use a text editor to edit or create the properties file with the following
entries:
clientHost=vdmservername.mycompany.com
clientPort=443
clientProtocol=https
If a properties file already exists containing entries with these key words, replace
the entries with new entries from this list.
2 Save the file.
3 Restart the VDM Security Server service so that the changes take effect. Click
Start>Administrative Tools>Services and select the VMware VDM Security
Server from the list of services. If the service is running, click Restart the service.
If the service is not running, click Start the service.
Tuesday, April 29, 2008
Monday, January 28, 2008
IdoNotes (and sleep)
New configuration setting prevents access to mail attachments
Use the NOTES.INI setting iNotes_WA_ReadAttachments to prevent access to an attachment in an e-mail.
Syntax: iNotes_WA_ReadAttachments=value
Description: Use this setting to prevent (turn off) access to attachments in e-mail. By default, any user can access an attachment in an e-mail. Using this setting prevents a users from accessing and copying sensitive information in an attachment at an unsecured workstation.
0= off (prevents access to attachments)
1= on (allows access to attachments)
Applies to: All Domino Web Access clients
Default: 1
IdoNotes (and sleep)
Domino Web Access 7 Customization
http://www.redbooks.ibm.com/redpieces/pdfs/redp4188.pdf
iNotes_WA_ReadAttachments
When set to 0, Domino Web Access users will not be able to read attachments. When set to
1, Domino Web Access users will be able to read attachments. The default is 1. There is also
functionality in Domino 7 to disable the ability to read attachments via an argument on the
URL. If &ra=0 is placed on the URL, the Domino Web Access user will not be able to read
attachments. The URL argument might be used to block particular users via a reverse proxy
rule or custom web page.
iNotes_WA_WriteAttachments
When set to 0, Domino Web Access users will not be able to write attachments. When set to
1, Domino Web Access users will be able to write attachments. The default is 1. There is also
functionality in Domino 7 to disable the ability to write attachments via an argument on the
URL. If &wa=0 is placed on the URL, the Domino Web Access user will not be able to write
attachments.
Use the NOTES.INI setting iNotes_WA_ReadAttachments to prevent access to an attachment in an e-mail.
Syntax: iNotes_WA_ReadAttachments=value
Description: Use this setting to prevent (turn off) access to attachments in e-mail. By default, any user can access an attachment in an e-mail. Using this setting prevents a users from accessing and copying sensitive information in an attachment at an unsecured workstation.
0= off (prevents access to attachments)
1= on (allows access to attachments)
Applies to: All Domino Web Access clients
Default: 1
IdoNotes (and sleep)
Domino Web Access 7 Customization
http://www.redbooks.ibm.com/redpieces/pdfs/redp4188.pdf
iNotes_WA_ReadAttachments
When set to 0, Domino Web Access users will not be able to read attachments. When set to
1, Domino Web Access users will be able to read attachments. The default is 1. There is also
functionality in Domino 7 to disable the ability to read attachments via an argument on the
URL. If &ra=0 is placed on the URL, the Domino Web Access user will not be able to read
attachments. The URL argument might be used to block particular users via a reverse proxy
rule or custom web page.
iNotes_WA_WriteAttachments
When set to 0, Domino Web Access users will not be able to write attachments. When set to
1, Domino Web Access users will be able to write attachments. The default is 1. There is also
functionality in Domino 7 to disable the ability to write attachments via an argument on the
URL. If &wa=0 is placed on the URL, the Domino Web Access user will not be able to write
attachments.
Subscribe to:
Posts (Atom)