7 Haziran 2012 Perşembe

Linksys - Cisco - Sipura IP telefonlarda "Daylight Saving Time Rule" parametresi

Türkiye için;

Yaz saati uygulaması Mart (3) ayının son (1) Pazar (7) günü saat 3:00 de (3) başlayıp Ekim (10) ayının son (1) pazar (7) günü saat 4:00 (4) de bitmektedir.

Daylight Saving Time Rule parametresi şu şekilde olmalı;

start=3/1/7/3;end=10/1/7/4;save=1

22 Mayıs 2012 Salı

Exchange 2010 da mailbox boyutlarını listelemek

Exchange 2010 GUI de maalesef mailbox boyutlarını görülemiyor. Exchange management shell de şu konmut çalıştırılırarak kullanıcıların mailbox boyutları listelenebilir.

Get-MailboxDatabase "" | Get-MailboxStatistics | Sort totalitemsize -desc | ft displayname, totalitemsize, itemcount

Bu komutun sonuna " > dosyaadi.txt " eklenerek bu çıktı bir text dosyasına alınabilir.

Olay Kimliği 1054 Grup İlkesi uygulaması başarısız oluyor

Olay Kimliği: 1054
Kaynak: Userenv

Windows XP client lar Group Policy almıyorlar.
rsop.msc çalıştırıldığı zaman hata alınıyor.

Registry e aşağıdaki değerleri girdiğim zaman düzeldi.

Registry subkey: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\System
Value name: GroupPolicyMinTransferRate
Value type: DWORD
Value Data: 0

Registry subkey: HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\System
Value name: GroupPolicyMinTransferRate
Value type: DWORD
Value Data: 0

16 Nisan 2012 Pazartesi

Virtual NUMA

Using Virtual NUMA
vSphere 5.0 introduces support for exposing virtual NUMA topology to guest operating systems, which can improve performance by facilitating guest operating system and application NUMA optimizations.
Virtual NUMA topology is available to hardware version 8 virtual machines and is enabled by default when the number of virtual CPUs is greater than eight. You can also manually influence virtual NUMA topology using advanced configuration options.
You can affect the virtual NUMA topology with two settings in the vSphere Client: number of virtual sockets and number of cores per socket for a virtual machine. If the number of cores per socket (cpuid.coresPerSocket) is greater than one, and the number of virtual cores in the virtual machine is greater than 8, the virtual NUMA node size matches the virtual socket size. If the number of cores per socket is less than or equal to one, virtual NUMA nodes are created to match the topology of the first physical host where the virtual machine is powered on.
When the number of virtual CPUs and the amount of memory used grow proportionately, you can use the default values. For virtual machines that consume a disproportionally large amount of memory, you can override the default values in one of the following ways:
Increase the number of virtual CPUs, even if this number of virtual CPUs is not used. See Change the Number of Virtual CPUs.
Use advanced options to control virtual NUMA topology and its mapping over physical NUMA topology. See Virtual NUMA Controls.
Change the Number of Virtual CPUs
You can configure a virtual machine that runs on an ESXi host to have up to 32 virtual CPUs.
Important
When you configure your virtual machine for multicore virtual CPU settings, you must ensure that your configuration complies with the requirements of the guest operating system EULA.
1
In the vSphere Client, right-click the virtual machine in the inventory and select Edit Settings.
2
Click the Hardware tab and select CPUs.
3
Select a value from the Number of virtual sockets drop-down menu.
4
Select a value from the Number of cores per socket drop-down menu.
The resulting total number of cores is a number equal to or less than the number of logical CPUs on the host.
5
Click OK.


Change the Number of Virtual CPUs
 
You can configure a virtual machine that runs on an ESXi host to have up to 32 virtual CPUs.
Important
When you configure your virtual machine for multicore virtual CPU settings, you must ensure that your configuration complies with the requirements of the guest operating system EULA.
1
In the vSphere Client, right-click the virtual machine in the inventory and select Edit Settings.
2
Click the Hardware tab and select CPUs.
3
Select a value from the Number of virtual sockets drop-down menu.
4
Select a value from the Number of cores per socket drop-down menu.
The resulting total number of cores is a number equal to or less than the number of logical CPUs on the host.
5
Click OK.


Virtual NUMA Controls
 
For virtual machines with disproportionately large memory consumption, you can use advanced options to manually override the default virtual CPU settings.
You can add these advanced options to the virtual machine configuration file.
Advanced Options for Virtual NUMA Controls
Option
Description
Default Value
cpuid.coresPerSocket
Determines the number of virtual cores per virtual CPU socket. If the value is greater than 1, also determines the size of virtual NUMA nodes if a virtual machine has a virtual NUMA topology. You can set this option if you know the exact virtual NUMA topology for each physical host.
1
numa.vcpu.maxPerVirtualNode
If cpuid.coresPerSocket is too restrictive as a power of two, you can set numa.vcpu.maxPerVirtualNode directly. In this case, do not set cpuid.coresPerSocket.
8
numa.autosize
When you set this option, the virtual NUMA topology has the same number of virtual CPUs per virtual node as there are cores on each physical node.
FALSE
numa.autosize.once
When you create a virtual machine template with these settings, the settings are guaranteed to remain the same every time you subsequently power on the virtual machine. The virtual NUMA topology will be reevaluated if the configured number of virtual CPUs on the virtual machine is modified.
TRUE
numa.vcpu.min
Minimum number of virtual CPUs in a virtual machine that are required in order to generate a virtual NUMA topology.
9
Note
When you set numa.autosize to TRUE, and if the configuration is set up manually or with a script, some guests might not be able to handle dynamic changes.
For example, a Linux application configured with the numactl system utility is set up and tested on one physical host with four cores per node. The host requires two NUMA nodes for a virtual machine with eight virtual CPUs. If the same virtual machine is run on a system with eight cores per node, which might occur during a vMotion operation, and numa.autosize is set to TRUE, only one virtual NUMA node will be created (rather than two virtual NUMA nodes). When numactl references the second virtual NUMA node, the operation will fail.
To avoid this, scripts should be intelligent enough to first query numactl --hardware. Otherwise, you must set the NUMA topology explicitly or allow the default numa.autosize.once setting to take effect.

Setting the number of cores per CPU in a virtual machine

Note: This feature is experimental in vSphere 4.0
 
Some operating system SKUs are hard-limited to run on a fixed number of CPUs. For example, Windows Server 2003 Standard Edition is limited to run on up to 4 CPUs. If you install this operating system on an 8-socket physical box, it runs on only 4 of the CPUs. The operating system takes advantage of multi-core CPUs so if your CPUs are dual core, Windows Server 2003 SE runs on up to 8 cores, and if you have quad-core CPUs, it runs on up to 16 cores, and so on.
 
Virtual CPUs (vCPU) in VMware virtual machines appear to the operating system as single core CPUs. So, just like in the example above, if you create a virtual machine with 8 vCPUs (which you can do with vSphere) the operating system sees 8 single core CPUs. If the operating system is Windows 2003 SE (limited to 4 CPUs) it only runs on 4 vCPUs.
 
Note: Remember that 1 vCPU maps onto a physical core not a physical CPU, so the virtual machine is actually getting to run on 4 cores.
 
Considering that 1 vCPU is equal to 1 CPU is an assumption for the sake of simplification, since vCPUs are scheduled on logical CPUs which are hardware execution contexts. These tasks can take a while in the case of a single core CPU, CPUs that have only 1 thread per core, or could be just a thread in the case of a CPU that has hyperthreading.
 
Consider this scenario:
 
In the physical world you can run Windows 2003 SE on up to 8 cores (using a 2-socket quad-core box) but in a virtual machine they can only run on 4 cores because VMware tells the operating system that each CPU has only 1 core per socket.
VMware now has a setting that provides you control over the number of cores per CPU in a virtual machine.
This new setting, which you can add to the virtual machine configuration (.vmx) file, lets you set the number of cores per virtual socket in the virtual machine.
 
To implement this feature:
  1. Power off the virtual machine.
  2. Right-click on the virtual machine and click Edit Settings.
  3. Click Hardware and select CPUs.
  4. Choose the number of virtual processors.
  5. Click the Options tab.
  6. Click General, in the Advanced options section.
  7. Click Configuration Parameters.
  8. Include cpuid.coresPerSocket in the Name column.
  9. Enter a value (try 2, 4, or 8) in the Value column.
    Notes: Ensure that the number of vCPUs is divisible by the number of  cpuid.coresPerSocket in the virtual machine. That is, when you divide the number of vCPUs by the number of cpuid.coresPerSocket, it must return an integer value. For example, if your virtual machine is created with 8 vCPUs, coresPerSocket can only be 1, 2, 4, or 8.

    The virtual machine now appears to the operating system as having multi-core CPUs with the number of cores per CPU given by the value that you provided in step 9.
  10. Click OK.

    For example:
Using 4 vCPU
Configuration you want
Settings needed for this configuration
Number of sockets
Number of cores per socket
Total cores
Set vCPU to:
Set cpuid.coresPerSocket/sockets to:
1
4
4
4
4
2
2
4
4
2










Using 8 vCPU
Configuration you want
Settings needed for this configuration
Number of sockets
Number of cores per socket
Total cores
Set vCPU to:
Set cpuid.coresPerSocket/sockets to:
1
8
8
8
8
2
4
8
8
4
4
2
8
8
2

Notes:
  • To be able to assign more than 4 vCPUs or if the processor supports more than 6 core(s) per processor, you have to assign an Enterprise Plus license, which supports up to 8 vCPUs and 12 core(s) per processor.
  • Only values of 1, 2, 4, 8 for the cpuid.coresPerSocket are supported for the multi-core vCPU feature in ESX 4.x.
  • In ESX 4.0, if multi-core vCPU is used, hot-plug vCPU is not permitted, even if it is available in the UI.
  • Only HV 7 virtual machines support the multi-core vCPU feature.
Important: When using cpuid.coresPerSocket, you should always ensure that you are in compliance with the requirements of your operating system EULA (that is, regarding the number of physical CPUs on which the operating system is actually running).

Additional Information

If you are using operating systems that were released when SMP was a high-end server-only, you expect that you need to do some tweaks such as selecting SMP kernel for Linux virtual machines and Multiprocessor PC HAL for Windows virtual machines.
 
Note: You do not encounter problems with recent operating systems. XP and newer and RHEL5 and newer either always install SMP kernel or automatically switch to it.
 
Some examples of the older operating system versions are:
  • RHel3-ES32
  • RHel3-ES64
  • RHel4.8-AS32
  • RHel4.7-ES32
  • RHel4.7-ES64
  • Win2000-Pro
  • Win2000-Serv
For information on:

28 Şubat 2012 Salı

Exchange 2010 Boş Gelen OWA Sayfası Çözümü


Exchange 2010 OWA sayfasın da herhangi hata alınamamasına rağmen sayfa boş geliyor.

Çözüm için Add Server Manager’ a gidin Roles ‘den IIS Server’ a sağ tıklayın ve Add roles’ ü seçerek
Aşağıdaki features ları yüklemesini sağlayın.  Bu işlemlerden sonar IIS ‘i restart etmeyi unutmayın.
Common HTTP Features

Static Content
Directory Browsing
HTTP Errors
HTTP Redirection

Health and Diagnostics

HTTP Logging
Logging Tools
Request Monitor
Tracing

25 Ağustos 2011 Perşembe

Internet Explorer Açılış Sayfasının Değişmemesi Problemini Düzeltmek

Öncelikle bilgisayarınızı Malware Byte's Anti Malware ya da Ad-aware gibi yazılımlar ile malware lere karşı tarayın. 
 
Internet başlangıç sayfasını değiştiremiyorsanız (yani ayarlarda silikseve aktif halde görünmüyorsa ) registrydeki

HKEY_CURRENT_USER\Software\Policies\Microsoft\
Internet Explorer\Control Panel anahtarını açın. Sağ tarafta bulunan HomePage REG_DWORD 0X00000001(1) değerin-
deki parantez içindeki (1) değerini (0) olarak değiştirin.


Ayarlarda başlangıç sayfası değişimi aktif hale geliyor fakat hala giriş sayfasını değiştiremiyorsanız;

HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main i açın sağ tarafta bulunan start page ve search page
deki yazan sayfa adreslerini kontrol edin. Çift tıklayarak dilediğiniz sayfa adreslerini girebilirsiniz

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main anahtarını açın sağ tarafta bulunan start page ve
search page deki yazan sayfa adreslerini kontrol edin. Çift tıklayarak dilediğiniz sayfa adreslerini girebilirsiniz.