okt 23

Windows 2012 R2 activate with KMS server

If you’re not using a brand new Windows Server 2012 R2 server as your KMS Server, you’ll need to download the relevant update.

If you don’t do this and try to activate, you’ll see the following message:

slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

So trust me, you need to install the patch and reboot.

Make sure you’re using the KMS Server key relevant to the OS you’re putting the key on, not what clients you’re planning to license (ie, KMS Server 2012 R2 key goes on any Server OS – 2008 to 2012, and will allow you to license both Windows Server 2012 R2 clients and Windows 8.1 clients).

Once you’ve successfully added the key with the slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx command, you can force it to activate with the command slmgr.vbs /ato. Normally it takes a few seconds for the dialog box to show the results.

You can then see the stats on how many KMS clients are activated, as well as checking that you’re ready for 8.1 and R2 with the command slmgr.vbs /dlv. Near the top of that dialog box will be a description which should end with VOLUME_KMS_2012-R2 channel.

You’re now good to go with the exciting world of KMS licensing on the latest operating systems from Microsoft. ®

okt 22

Windows 8.1 Update error 0x800705AA

Error 0x800705AA when you try to upgrade a Windows 8-based virtual machine to Windows 8.1

windows 8.1 error

 

 

 

 

 

 

 

 

 

 

Couldn’t update to Windows 8.1
Sorry we couldn’t complete the update to Windows 8.1 We’ve restored your previous version of Windows to this pc.
0x800705AA – 0x2000C

Certain phases of the upgrade require more memory than the default startup RAM (512 megabytes [MB]). This issue occurs because dynamic memory isn’t enabled during those phases of the upgrade.

windows 8.1 RAM

 

 

 

 

 

 

 

 

 

 

 

To work around the issue, increase the startup RAM for the VM to 2 gigabytes (GB) in the Hyper-V manager before you upgrade. You can set the startup RAM back to the default after the upgrade is complete.

windows 8.1 RAM 2048

 

 

 

 

 

 

 

 

 

 

 

http://support.microsoft.com/kb/2878739

 

mei 11

Outlook agenda syncen met 2 gmail agenda’s naar iphone

Probleem: Je wilt je outlook syncen naar 2 verschillende agenda’s en deze kunnen bekijken op je iphone.

Installeer op je pc of laptop waar je outlook op staat het programma : Google calendar sync

Configureer deze zodat deze gesynchroniseerd wordt met je eerste gmail account.

Deel deze eerste gmail agenda met het tweede gmail account.

Log in op je gmail account en druk op deze link  https://www.google.com/calendar/b/0/iphoneselect

Als het goed is staat je gedeelde agenda hierbij en hoef je alleen een vinkje te zetten.

 

 

 

 

feb 10

EsxPress backup problem

Problem:
Problem in creating a template by cloning the Live VM of a Windows Server 2003 x64 Edition

Here it is the error message:

Creating snapshot of Virtual Machine

Cannot create a quiesced snapshot because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.

I’ve installed the VMWare tools, Upgraded the VM Hardware to be v7 and make sure that the VSS service are all ON but still it failed.

SOLUTION:
1. Backup the following regkey: HKLM\Software\Microsoft\EventSystem\
2. Erase the regkey HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216} an below
3. Reboot.
4. Verify that things are working by running

vssadmin list writers
vssadmin list providers.

and then in the services.msc list of services snap ins, make sure the following services are Started Automatically:

1. COM+ System Application
2. Distributed Transaction Coordinator
3. Volume Shadow Copy
4. VMware Physical Disk Helper Service

Automatically but not started:

1. Microsoft Software Shadow Copy Provider
2. VMware Snapshot Provider

now the backup is all working great

dec 03

Provider is not capable of the attempted operation (0×80041024) when using wbemtest

Provider is not capable of the attempted operation (0×80041024) when using wbemtest

When trying to set the External addresses for the Group Expansion Server, The Address Book Files and the Meeting Content Download you would normally use WBEMTEST to set the WMI parameters.

In a normal scenario, you would open each of the relevant objects e.g. MSFT_SIPAddressBookSetting, and click the “Instances” button. It seems that with OCS 2007 R2 you can’t do that. You get an error like the following;

Number: 0×80041024

Facility: WMI

Description: Provider is not capable of the attempted operation

Instead of doing that, you have to do a query for any instances and in particular, you have to specify “where backend=xxxx” as part of the query. So for example if you have an Enterprise pool with SQL installed as the default instance, the query would be as follows;

select * from MSFT_SIPAddressBookSetting where backend=”mysqlserver”

Detailed information on this is provided in the following Microsoft Support Article (http://support.microsoft.com/kb/938288).

dec 02

OCS 2007 R2 error: 3287185656 (0xC3EE78F8)

When you update your OCS servers with ServerUpdateInstaller.exe you may receive the following error on the Front-End server: The Office Communications Server Front-End service terminated with service-specific error 3287185656 (0xC3EE78F8).

The solution is to install first the OCS2009-DBUpgrade.msi before ServerUpdateInstaller.exe

Link: http://support.microsoft.com/kb/968802

okt 18

Google maps not working on IE7 and IE6

Since a couple of days http://maps.google.com is not working anymore on internet explorer 6 and internet explorer 7.
On internet explorer 8 everything is working fine.
You get the message that the internet explorer is aborting.

More information you can find here:
http://www.google.com/support/forum/p/maps/thread?tid=3f95fa8fc93638c5&hl=en

The fix you can download here:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c77ee103-7e97-44b2-bbf3-ee9f0de37fed

okt 13

Exchange 2007, export mailbox to .pst file

What Data Is Exported

By default, the Export-Mailbox cmdlet exports all empty folders, special folders, and subfolders to the target location. To specify which folders to include in the export, use the IncludeFolders parameter. To specify which folders to exclude from the export, use the ExcludeFolders parameter.

By default, the following special folders are exported when you use the Export-Mailbox cmdlet:

  • Inbox
  • Deleted Items
  • Drafts
  • Junk E-Mail
  • Outbox
  • Sent Items
  • Journal
  • Calendar
  • Contacts
  • Notes
  • Tasks

The Export-Mailbox cmdlet exports all message types, including messages, calendar items, contacts, distribution lists, journal entries, tasks, notes, and documents. However, the Export-Mailbox cmdlet does not export rules.

The Export-Mailbox cmdlet also exports messages from the dumpster. Messages from the dumpster are converted to regular items in the folder or .pst file to which you export data

Before You BeginTo perform this procedure, the account you use must be delegated the following:

  • Exchange Server Administrators role and local Administrators group for the source server and the target server
  • Full access to the source and target mailboxes

For more information about permissions, delegating roles, and the rights that are required to administer Exchange 2007, see Permission Considerations.

Also, before you perform this procedure, be aware of the following:

  • To use the Export-Mailbox cmdlet, the source mailbox and target mailbox must be in the same forest. You cannot export data from a mailbox in one forest to a mailbox in a different forest.
  • You cannot export data from a public folder database.
  • To grant full access to a mailbox, use the Add-MailboxPermission cmdlet and specify FullAccess for the AccessRights parameter. For example, if Admin01 needs to export data from John’s mailbox to a mailbox called Export, you must first run the following commands:
    Add-MailboxPermission -Identity john -User Admin01 -AccessRights FullAccess
    Add-MailboxPermission -Identity Export -User Admin01 -AccessRights FullAccess
  • To export data from an Exchange 2003 or Exchange 2000 mailbox, the account you use must be delegated the Exchange Administrator role for the administrative group in which the server resides.
  • To export data from a .pst file, you must run the Export-Mailbox cmdlet from a 32-bit computer that has the following installed:
    • The 32-bit version of the Exchange management tools
    • Outlook 2003 Service Pack 2 (SP2) or Outlook 2007

    For information about Exchange 2007 management tools 32-bit download, see Microsoft Exchange Server 2007 Management Tools (32-Bit).

  • If you export data to a folder in another mailbox, the target mailbox that you specify must exist before you run the command
  • To export data to a .pst file, run the following command:
    Export-Mailbox -Identity <MailboxIdParameter> -PSTFolderPath <Path_Of_PST_Folder>\<File_Name>.pst

    More information and options :
    http://technet.microsoft.com/en-us/library/bb266964(EXCHG.80).aspx

    okt 01

    Changing Passwords and Accounts in MOM

    You might need to change the passwords of MOM accounts, because your security policy might require passwords to expire and be changed on a regular basis. When you do this, there is a best sequence to follow:

    Changing the Management Server Action Account Password

    1. Change the accounts password on the local computer or the domain. If this is a local account you can do this using the Local Users and Groups snap-in. If this is a domain account, you can use the Active Directory Users and Computers snap-in.
    2. Change the password that MOM uses by using the SetActionAccount.exe utility. Directions for this utility are in the “Action Account Password Changes” section of this guide.
    3. Restart the MOM Service on the Management Server.

    Changing the MOM Agent Action Account Password

    1. Change the accounts password on the local computer or the domain. If this is a local account you can do this using the Local Users and Groups snap-in. If this is a domain account, you can use the Active Directory Users and Computers snap-in.
    2. Change the password that MOM uses by using the SetActionAccount.exe utility. Directions for this utility are in the “Action Account Password Changes” section of this guide.
    3. Restart the MOM Service on the managed computer.

    Changing the DAS Account Password

    1. Change the accounts password on the local computer or the domain. If this is a local account you can do this using the Local Users and Groups snap-in. If this is a domain account, you can use the Active Directory Users and Computers snap-in.
    2. Update the password for the Identity for the Microsoft Operations Manager Data Access Server COM+ application. You can do this in the Component Services snap-in.
    3. Stop the COM+ application and then restart it.

    Note

        If you are changing the Management Server Action Account and the DAS account at the same time, you must change the Action Account first, then the DAS account, and then stop the MOM Service before stopping the COM+ application. Starting the MOM Service will also start the COM+ application.

    If the MOM Service will not start, it might be because the DAS account has not been changed properly or the password has expired.

    Changing the DAS Account

    You can change which account MOM uses for the Data Access Service (DAS) functionality. The account must be a domain account with at least the following properties:

    • Member of the MOM Users group on the Management Server.
    • A SQL Server Logon with “Permit” server access and “db_owner” (DBO) access to the OnePoint database on the MOM Database Server.
    • A SQL Server Security Login with “Permit” server access.
    • The DAS account must also be a member of the SC DW DTS security groups on the MOM Reporting Server and MOM Database Server, if MMPC is installed using the DAS account.

    sep 30

    How to Groom and Shrink a Reporting database

    We had a MOM 2005 reporting database which had not been archiving correctly and had grown to the point that there wasn’t enough free disk space to run the grooming process, due to increases in the size of the log files. Based on business requirements and hardware constraints the decision was made to trim down the content of the reporting database down to 35 days from what was originally data that was more than 500 days old. The original database size was approximately 55 GB with no free space, after successful grooming it was moved down to .5 GB (prior to re-activating the DTS package to transfer from the Operations database to the reporting database).

    To accomplish this, we took the following high level process (all scripts referred to are included in full below):

    Scripts

    Check Grooming

    This script checks the current state of the grooming settings.
     
    SELECT cs.cs_tablename ‘Table Name’, wcs.wcs_groomdays ‘Groom Days’ from warehouseclassschema wcs
    Join classschemas cs
    On cs.cs_classID = wcs.wcs_classID
    Where cs.cs_tablename = ‘SC_AlertFact_Table’
    And wcs.wcs_mustbegroomed = 1
     
    SELECT cs.cs_tablename ‘Table Name’, wcs.wcs_groomdays ‘Groom Days’ from warehouseclassschema wcs
    Join classschemas cs
    On cs.cs_classID = wcs.wcs_classID
    Where cs.cs_tablename = ‘SC_AlertHistoryFact_Table’
    And wcs.wcs_mustbegroomed = 1
     
    SELECT cs.cs_tablename ‘Table Name’, wcs.wcs_groomdays ‘Groom Days’ from warehouseclassschema wcs
    Join classschemas cs
    On cs.cs_classID = wcs.wcs_classID
    Where cs.cs_tablename = ‘SC_AlertToEventFact_Table’
    And wcs.wcs_mustbegroomed = 1
     
    SELECT cs.cs_tablename ‘Table Name’, wcs.wcs_groomdays ‘Groom Days’ from warehouseclassschema wcs
    Join classschemas cs
    On cs.cs_classID = wcs.wcs_classID
    Where cs.cs_tablename = ‘SC_EventFact_Table’
    And wcs.wcs_mustbegroomed = 1
     
    SELECT cs.cs_tablename ‘Table Name’, wcs.wcs_groomdays ‘Groom Days’ from warehouseclassschema wcs
    Join classschemas cs
    On cs.cs_classID = wcs.wcs_classID
    Where cs.cs_tablename = ‘SC_EventParameterFact_Table’
    And wcs.wcs_mustbegroomed = 1
     
    SELECT cs.cs_tablename ‘Table Name’, wcs.wcs_groomdays ‘Groom Days’ from warehouseclassschema wcs
    Join classschemas cs
    On cs.cs_classID = wcs.wcs_classID
    Where cs.cs_tablename = ‘SC_SampledNumericDataFact_Table’
    And wcs.wcs_mustbegroomed = 1
     

    Set Grooming

    Set the grooming date on each of the six fact tables. The last number will vary depending on what the grooming interval needs to be configured for.
     
    Exec p_updategroomdays SC_AlertFact_Table, 700
    Exec p_updategroomdays SC_AlertHistoryFact_Table, 700
    Exec p_updategroomdays SC_AlertToEventFact_Table, 700
    Exec p_updategroomdays SC_EventFact_Table, 700
    Exec p_updategroomdays SC_EventParameterFact_Table, 700
    Exec p_updategroomdays SC_SampledNumericDataFact_Table, 700
     

    Table Count

    Identify the total number of records in each of the fact tables for later comparison.
     
    select count(*) from SC_AlertFact_Table
    select count(*) from SC_AlertHistoryFact_Table
    select count(*) from SC_AlertToEventFact_Table
    select count(*) from SC_EventFact_Table
    select count(*) from SC_EventParameterFact_Table
    select count(*) from SC_SampledNumericDataFact_Table
      

    Oldest Date

    Identified the oldest data in the database through the following queries: (very slow to run).
     
    SET ROWCOUNT 2
    select DateTimeLastModified from SC_AlertFact_Table order by DateTimeLastModified
    select DateTimeLastModified from SC_AlertHistoryFact_Table order by DateTimeLastModified
    select DateTimeAlertAdded from SC_AlertToEventFact_Table order by DateTimeAlertAdded
    select DateTimeGenerated from SC_EventFact_Table order by DateTimeGenerated
    select DateTimeEventStored from SC_EventParameterFact_Table order by DateTimeEventStored
    select DateTimeAdded from SC_SampledNumericDataFact_Table order by DateTimeAdded
     

    Date Diff

    Based upon the results of the oldest records, identify the oldest date in the database through using a difference in dates (the first date is the oldest date found in the fact tables)
     
    select datediff (day, ’2005-10-27′, getdate())

    Truncate Log

    To clear out the SystemCenter Reporting log files.

    BACKUP LOG SystemCenterReporting with TRUNCATE_ONLY

     

    Shrinkfile

    To shrink the reporting database.
     
    dbcc shrinkfile(REPLOG,2)
    BACKUP LOG SystemCenterReporting WITH TRUNCATE_ONLY
    dbcc shrinkfile(REPDATA,2) 

     

    1. Identify the count of each of the 6 fact tables using the “Table Count” script, and keep track of those statistics going forward.
    2. Identify the oldest data in the tables using the “Oldest Date” script.
    3. Determine the date difference between the oldest date and the current date with the “Date Diff” script.
    4. Set the grooming interval to higher than the highest date using the “Set Grooming” script. This is done to ensure the grooming process will work as long as there is no data that needs to be groomed.
    5. Verify the change tot he grooming settings with the “Check Grooming” script.
    6. Start the reporting grooming job (called SCDWGroomJob) in the SQL Agent jobs section of the SQL 2000 Enterprise Manager.
    7. When the job (hopefully!) succeeds, run the “Truncate Log” script to free up some of the transaction log space.
    8. Change the grooming setting to slightly less than the highest difference so that the next grooming job will be configured to actually groom out data.
    9. Re-run steps 5 though 8 for the new setting.
    10. Continue this process with decreasing values (the oldest data in the database we were working through was 508 days!). For that particular environment we were grooming settings which decreased from: 700, 500, 400, 350, 275, 200, 125, 35.
    11. Finally we were able to decrease the size of the reporting database through the “Shrinkfile” script.
    12. Last, w reactivated the scheduled task to move data from the Operations database to the Reporting database and started growing the data again; but this time up to a maximum of 35 days.

    Fact Table Statistics:             700 Days         400 Days         350 Days         275 Days

    AlertFact                                          715                  715                 715                  715
    AlertHistoryFact                            32,184             27,919             21,481             15,748
    AlertToEventFact                          38,969             34,123             27,609             21,151
    EventFact                                4,415,065         4,291,870        4,079,922         3,862,984
    EventParameterFact                    828,708           828,708            828,708            828,708
    SampledNumericDataFact      152,648,971     138,060,142     121,863,087       98,431,535

    Fact Table Statistics:             200 Days         125 Days          35 Days

    AlertFact                                          715                  715                  26
    AlertHistoryFact                              9,234                3,051                   1
    AlertToEventFact                          17,230                8,467                   5
    EventFact                                3,752,214          3,022,275             3,625
    EventParameterFact                    828,708             828,708             3,315
    SampledNumericDataFact        87,401,639        47,819,874          413,745