Friday, 17 January 2014

VMWare'de sistem uyarı tonlarını iptal etmek.

VMWare'de sistem uyarı tonlarını iptal etmek.
Eğer sesli sistem uyarı tonunu belirli bir sanal makine için iptal etmek istiyorsanız.

VM'e ait .vmx dosyasına aşağıdaki satırı notepad aracılığı ile ekleyip kaydedin sanal makine kapalı iken.
mks.noBeep = "TRUE"

Eğer bunu tüm sanal makineler için gerçekleştirmek istiyorsanız aynı ekleme işlemini global konfigürasyon dosyaı olan config / config.ini üzerinde yapmalısınız.

Benim sunucumda C:\ProgramData\VMware\VMware Workstation altında idi.

Eğer dosya yoksa yaratmanız da mümkün.

vmware_dis_beeps

How to disable VMWare PC Speaker System Beeps

How to disable VMWare PC Speaker System Beeps
Annoying isn't it.

So if you want to disable / turn off VMWare PC speaker system beeps for a specific virtual machine

Edit the VM's .vmx file, add the line below and save it while machine is OFF.
mks.noBeep = "TRUE"

If you want to disable it for all VMs you need to add same line to global configuration file  called config / config.ini.

In my case it was located under C:\ProgramData\VMware\VMware Workstation.

You can also create one if it doesn't exist.

vmware_dis_beeps

 

Thursday, 16 January 2014

SCCM Failed to create task sequence media errors

I'd like to share some errors and their solutions those worked for me during creating task sequence media in SCCM.

Error 1: Error creating media. Error message is : The hash value is not correct. 0x8(Hash could not be matched for the downloaded content. ) Please refer to CreateTsMedia.log to get details.

Open CreateTsMedia.log file (<ConfigMgrInstallationPath>\AdminUILog\AdminUILog)

The error in my case was:

Staging package CAM0011D
Before executing state - fsVolumeSpaceRemaining= 6844 Mb
Staging package CAM0011D
Hash could not be matched for the downloaded content. Original ContentHash = 37EF10E36133D3F00B3A18D36AAC6ED36F38DBC3, Downloaded ContentHash = F641FD184FA74E192FBED1F72B4CD19FA3683216
Failed to stage package CAM0011D (0x80091007)
Failed to create media (0x80091007)
CreateTsMedia failed with error 0x80091007, details="CAM0011D"
MediaGenerator::~MediaGenerator()

To fix: Select the Task Sequence you are about the create Task Sequence Media, then click references in the tabs below and locate the package mentioned in logs, it was CAM0011D in my case. Then refresh the package on failing DP, if it won't help you can delete the PCK from the DP and refresh it again to send it again. Or you can directly update the package (Update Distribution Points) and try again when new source version installed to DPs.

 

Error 2: Error creating media. Error message is : The hash value is not correct. 0x80091007 (Hash could not be matched for the downloaded content. ) Please refer to CreateTsMedia.log to get details.

Open CreateTsMedia.log file (<ConfigMgrInstallationPath>\AdminUILog\AdminUILog)

The error in my case was:

Finished adding client config policies and policy assignments
Setting up Install Toolkit
Hash could not be matched for the downloded content. Original ContentHash = C..., Downloaded ContentHash = 5...
Failed to create media generator (0x80091007) 
CreateTsMedia failed with error 0x80091007, details=""

To fix: The problem of this error is lack of details. Because it doesn't say which package caused the problem as the Error1 above. What I found is from the temporary working folder is it generates this error just after retrieving the boot image associated to Task Sequence. So refreshing boot image (actually I had to remove it and add the DP again because of another problem.) is helps as in Fix1 above.

 

 

Error 3: Failed to create media

This time the error in my case was:

Beginning media generation
Failed to find the volume for system partition, it might be drive letterless
Marking partitions active is only supported for MBR disks.
Unable to activate partition (0x80004001)
Error formatting volume G:\ (0x80004001)
Failed to create media (0x80004001)
CreateTsMedia failed with error 0x80004001, details=""
MediaGenerator::~MediaGenerator()

To fix: We need to re-partition the USB media and be sure it has marked as active. I used diskpart to do that. Steps are below.

Run diskpart with administrative rights

diskpart
list disk (find your USB disk number)
select disk 2 (2 here is the number of the USB disk listed in list disk command)
WARNING: The next command (clean) will wipe the disk you have just selected above.
Please be sure you have selected the correct disk.
clean (to clean partitions)
create partition primary size=16384 (to create a 16GB primary partition)
list par (to list partitions in the selected disk)
select partition 1 (select the partition you have just created, there should be only one)
active (mark the partition as active)
assign letter=G (any avail. letter)
format fs=ntfs quick label=”TSMedia” (format the partition quickly with NTFS and naming (label is up to you))
exit (done)

usbtsmediadiskpart

usbtsmediapar

 

Now you can try to create your USB media again.

Hope it helps or gives an idea.

Friday, 10 January 2014

Haber: SCCM 2012 SQL Server Views dokümantasyonu yayınlandı.

SCCM ürün takımı SCCM 2012 için SQL Server Views dokümantasyonunu yayınladı.

Yeni dokümantasyonu aşağıdaki TechNet adresinde bulabilirsiniz.

Creating Custom Reports by Using SQL Server Views in System Center 2012 Configuration Manager

Dokümantasyon genel olarak üç ana bölüme ayrılmış:



 

News: SQL Server Views documentation for SCCM 2012

SCCM Team has announced the SQL Server Views documentation for System Center 2012 Configuration Manager is now available.

You will find the new documentation on TechNet at the following URL:

Creating Custom Reports by Using SQL Server Views in System Center 2012 Configuration Manager

This documentation is split into three sections:

Thursday, 9 January 2014

Failed to validate delegation token. Reason: InvalidExpired

When you test the Federation Trust that you have created between your On-Premise Exchange environment and the Microsoft Federated Gateway the Token Validation fails with the message 'Failed to validate delegation token' run the same command with the -Verbose switch to see detailed information on the error.

DelegationToken_InvalidExpired1

If the reason is appears is InvalidExpired this can be due to a time difference problem between your server and MS Federated Gateway service.

So you will need to configure an authoritative time server on your side. The MS article How to configure an authoritative time server in Windows Server  provides detailed information about configuring NTP , you can use the manual steps to accomplish it or use Fix It utilities provided. You can run the following command to set the time service to synchronise with an external time service.

  • w32tm /config /manualpeerlist:time.windows.com /syncfromflags:manual /reliable:yes /update

  • net stop w32time

  • net start w32time


After restarting the time service ensure that the system is synchronising the time with the source set in the above step successfully.

DelegationToken_InvalidExpired2

Re-run the Test-FederationTrust command. This time the delegation token should be displayed as valid.

DelegationToken_InvalidExpired3

 

ecsword

Monday, 6 January 2014

Test-FederationTrust couldn't find object extest

When you run Test-FederationTrust cmdlet; it fails with the error 'Couldn't find object "extest_<random number>". Please make sure that it was spelled correctly or specify a different object'.

fd1

The reason for this is because the 'extest_<random number>' user object that the system is trying to run the cmdlet with, does not exist in Active Directory. To skip this error message Run the Test-FederationTrust cmdlet as follows:

  • Test-FederationTrust -USerIdentity "Existing User Alias"


ecsword