Hüseyin Göksin Blog

Bilgi paylaştıkça çoğalır….

Windows7 Profile Temp Sorunu…

ilk önce eski profile’nın adı değiştirilir yedek olsun diye sonra aşşağıdaki işlemler yapılır.

Delete C:\Users\%username%
Delete C:\Users\TEMP
Delete the registry key matching your SID from
“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\ProfileList” altındaki herşeyi silin reboot sonrasında normale dönecektir.

 

Hüseyin Göksin

Filed under: Uncategorized

2008 yada 2003 server’da dosya yetkileri aşşağıdaki yerdedir.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares]

Filed under: Server2008

ESXI 5.5 static mac address “conflicts with VMware reserved MACs”

esxi-error-5-mc-chang

You may see above error in ESXI 5.5 after changing dynamically generated MAC address to STATIC mac address dueto application MAC bind restriction.

In new ESXI 5.5 ,  new policies have been added where the statically assigned MAC addresses can only be in the range 00:50:56:xx:xx:xx series, If you try to change it to something else and then power on the guest machine, you may see above error.

Few days before, a friend of mine upgraded his ESXI from ver 5.0 to 5.5. One of his guest application was binded with the MAC address and the new esxi 5.5 doesn’t allow to use that specific series mac address. So I googled and found following solution that worked (at least for me 😉 )

To RESOLVE this issue, follow this.

1- Enable SSH in ESXI Server Configuration

2- Turn off the target guest machine and change the mac address as per your requirements for the required interface.

3- Turn off the V-Sphere ESXI client.

3- Login to ESXI server via SSH using any ssh client like PUTTY

4- Goto your data store / guest machine folder and open the VMX file.

.

For example I have guest machine with ‘123‘ name. So I used following

~ # cd /vmfs/volumes/
/vmfs/volumes # ls

52a18cdd-49376389-86aa-000c29d1de32  61031d71-0233e8da-be74-f942274c16c3
52a18ce5-9d0863e6-e50b-000c29d1de32  8901537a-ad66db83-fd1f-38ac926cce01
52a18ce7-bd9d6e2a-dacf-000c29d1de32  datastore1
/vmfs/volumes #

/vmfs/volumes # cd datastore1/
/vmfs/volumes/52a18ce5-9d0863e6-e50b-000c29d1de32 # ls
123

/vmfs/volumes/52a18ce5-9d0863e6-e50b-000c29d1de32 # cd 123
/vmfs/volumes/52a18ce5-9d0863e6-e50b-000c29d1de32/123 # ls

123-flat.vmdk               vmware-14.log
123.nvram                     123.vmxf                      vmware-15.log
123.vmdk                      vmware-11.log                 vmware-16.log
123.vmsd                      vmware-12.log                 vmware.log
123.vmx                       vmware-13.log

As showed in the image below . . .

3-putty-ssh

Now open the VMX file of the guest machine.

for example

1
vi 123.vmx

now press I and add this line anywhere.

1
ethernet0.checkMACAddress = "false"

(Change the ethernet0 to match your local ethernet number)

Now save and exit it by pressing :wq

Now start V-Sphere ESXI client and start the machine as you normally do 🙂

Congrats you are UP with new MAC address activated 😀

SAMPLE .VMX FILE FOR STATIC MAC address

Following is an sample of working .vmx file for static mac address.

1
2
3
4
5
ethernet0.networkName = "LAN"
ethernet0.addressType = "static"
ethernet0.present = "TRUE"
ethernet0.checkMACAddress = "false"
ethernet0.address = "00:0C:29:Ha:Ha:Ho"

Filed under: Esx Ailesi

Aktif-Server-Pc Adları ve OS

DİKKAT EDİLECEK NOKTALAR

1. Kodlar Windows Server 2008 yüklü olan bir etki alanı sunucusunda çalıştırılmalıdır.

 

Yöntem 1 (Adım Adım)

  1. Windows Server 2008 ve ya üzeri ile çalışan bir etki alanı sunucusuna bağlanın ve PowerShell  (PS) ekranını açın;
  2. Import-Module ActiveDirectory” komutu ile aktif dizin bileşenlerini yükleyin;
  3. $today = Get-Date” Komut ile günü belirleyin;
  4. $cutoffdate = $today.AddDays(-60)” Komutu ile 60 gün içerisinde sisteme kaydolmuş istemcileri filtreleyin;
  5. Get-ADComputer  -Properties * -Filter {LastLogonDate -gt $cutoffdate} | Select Name,OperatingSystem,OperatingSystemVersion, LastLogonDate,CanonicalName | Export-Csv ./ActiveComputers.csv” Komutu ile dosyayı oluşturun;

 

Filed under: Server2008

Brigt Mail Yer Sorunu Log silme.

      1. Quarantined messages:

        • Make sure to regularly delete old messages from the quarantine in Spam > Email Spam.
        • You can automate this process by going to Spam > Quarantine settings. Under the “Spam Quarantine Expunger” heading, set some thresholds and ensure that messages are expunged regularly.

 

      2. Compliance incidents:

        • Make sure to regularly delete old incidents from the incident folders in Content > Incident Management.
        • You can keep a record of your incidents by exporting them with the “Export Incident History” button.

 

      3. Reporting data:

        • You can manually delete reporting data in Administration > Reports, and click on “Delete Data Now”.
        • The Brightmail Gateway is set to expunge reporting data older than 7 days. You can adjust this to your needs.

 

      4. Logging database:

        • You can manually clear all scanner logs from the log database by going to Status > Logs and clicking on “Clear All Scanner Logs”
        • The Brightmail Gateway is configured to expunge the log database once logs are 7 days or older, and has a default maximum log size of 50MB. You can adjust this in Administration > Logs

 

      5. Database backups:

        • You can download or delete old backups in Administration > Version > Restore/Download

 

      6. Message Audit Logs:

        • You can backup the Message Audit Logs from each scanner to a remote server using the admin CLI command “mallog”. The command supports scp/ftp to backup and scp/ftp and http to restore.
        • You can manually clear all Message Audit Logs from the scanners by using the admin CLI commands below:

      (a) On versions 8.0 and older the admin CLI command is “clear mallogs”

 

      (b) On versions 9.0 and later the admin CLI command is “delete mallogs”

Filed under: Uncategorized

Proxy win7 sorunu

  • [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
    • "ProxyEnable"=dword:00000001
    • "ProxyServer"="10.1.1.12:8080"
    • "ProxyOverride"="http://*.internal.lan;https://*.internal.com;<local>

Registry Settings in the Group Policy Editor

 

Filed under: Uncategorized