How to Fix Outlook Reminders

A populair feature of Microsoft Outlook is the Outlook calendar ability to recieve reminders for scheduled meetings and tasks. If these reminders appearing at incorrect time or not showing at all. The option to show reminders is likely disabled or the file is corrupted. By checking the status of the feature, enabling it if necessary and fixing corrupt entries, you can fix this issue and reinstate correct reminders in Outlook.

Start Microsoft Outlook. Go to the “Tools” menu in Outlook 2003 or 2007 and select “Options.” Select “Other,” click the “Advanced Options” button and choose “Reminder Options.” In Outlook 2010, go to the “File” tab and click “Options.” Select the “Advanced” tab in the left pane and find the “Reminders” section.
Make sure that the “Display the Reminder” check box is selected in Outlook 2003 or 2007. In Outlook 2010, make sure the “Show Reminders” check box is selected. Click “OK.” If the check box was not selected, enabling it will fix the problem. If it was already selected, continue on to fix corrupt reminder files.
Exit Microsoft Outlook. In Windows XP, click the “Start” button and select “Run.” Type “outlook /cleanreminders” into the Open box and click “OK.” In Windows Vista or Windows 7, click “Start” and type “outlook /cleanreminders” into the Search box at the bottom of the Start Menu. Select “Outlook/Clean Reminders” from the result list. Microsoft Outlook opens.
Check to see if your Outlook reminders are now working. If so, the “Outlook /Clean Reminders” switch has fixed the problem. If not, continue on to the final step.
Click the “Start” button and select “Run” in Windows XP Type “outlook /resetfolders” into the Open box and click “OK.” In Windows Vista or Windows 7, click “Start” and type “outlook /resetfolders” into the Search box at the bottom of the “Start Menu.” Select “Outlook/Reset Folders” from the result list. Microsoft Outlook opens with the missing or corrupt reminder folders restored.

If the above steps does not solve your problem go to the next few steps..

Open your internet browser and go to your OWA site, some companys use In OWA 2010 you will see in the upper right corner an number, These represents your current open appointments and tasks.. Click on the open appointments and sellect “dismiss all” Exchange will reset the current appointments and appointments will reapair when you restart Outlook on your desktop.

SCCM Client FIX, WMI Repository corruption

The WMI Repository is the data database “%windir%\system32\wbem\repository” That stores meta-information and definitions for WMI Classes. In some cases the repository also stores static class data as well. If the Repository becomes corrupted, then the WMI service will not be able to function correctly. SCCM is build to use the WMI repository to work.

If you suspect that the WMI repository is corrupted the last thing you should do is rebuilding and deleting the repository, †it could damage your windows installation and let fail applications. Other steps need to be taken first to confirm that the repository is truly corrupted. A large repository could cause problems and†sometimes be interpreted as a corrupt repository, which is not always the case. If issues are due to a large repository, rebuilding the repository is currently the only method available to reduce the repository size.
Before you take anysteps make sure you used WMIdiag†to report any problems with the repository.
If repository is found to be inconsistent:
††† a. For Vista and newer, run from elevated command prompt:
Winmgmt /salvagerepository
Note†this command will take the content of the inconsistent repository and merge it into the rebuilt repository if it is readable
If the above doesnít work, then run:
Winmgmt /resetrepository
Note†this will reset repository to the initial state when the OS was first installed.
Note†In Windows XP and Windows Server 2003 there is no posibility to use switches for repairing the†repository.
Warning: Rebuilding the WMI repository has resulted in some 3rd party products not working until their setup is re-run & their MOF re-added back to the repository.
If /salvagerepository or /resetrepository does not resolve the issue, then manually rebuild repository:
  1. Open a CMD prompt with elevated privileges
  2. Use “net stop winmgmt” to stop the WMI services
  3. Rename the repository folder:† C:\WINDOWS\system32\wbem\Repository to Repository.old
  4. CD windows\system32\wbem
  5. for /f %s in (‘dir /b /s *.dll’) do regsvr32 /s %s
  6. Use “net start winmgmt” to start the WMI services
  7. cd /d c:\† ((go to the root of the c drive, this is important))
  8. for /f %s in (‘dir /s /b *.mof *.mfl’) do mofcomp %s
  9. Reboot the server or client

Het leed dat License Key heet

Op het moment in 2002 toen Windows XP uitkwam was er ruim 35 dagen voor het

uitkomen de OEM-SPL Licentie bekend die OEM bouwers zoals DELL, HP, Packer Bell gebruiken om een single preimaged systeem te activeren. in 2004 Heeft microsoft WGA geÔntroduceerd. Hiermee werden hacks om eigen licentie key’s te activeren moeilijker gemaakt maar niet onmogelijk.

Vandaag was ik bij een klant die een virus had op zijn computer. De machine gaf al snel een BSOD met de meldi
ng 0x0000007B deze melding houd eigenlijk in dat de SATA drivers niet geladen kunnen worden. Oplossing is vaak windows opnieuw te installeren en de machine terug in het netwerk plaatsen. Echter Windows installeren is vaak het probleem niet, maar het instellen van de License key.
Na de installatie van Windows XP SP2 kwamen we in het login scherm. Echter bij het proberen in te loggen op de machine moesten we direct de machine activeren. Normaal geen probleem, alleen nu omdat de netwerk kaart niet was geÔnstalleerd konden we niet via het internet activeren. Hierom de telefonische keuze gemaakt. Hierbij heb je een 5×5 cijferig †key Product ID die je telefonisch moet opgeven. Hierna krijg je een gegenereerde code terug die je zelf moet intikken in windows en het systeem is geactiveerd. Helaas werd deze code niet gegenereerd. Ook omdat we niet konden inloggen en het systeem niet in konden getracht een ander installatie medium te gebruiken. Hierbij dezelfde uitkomst, wel konden we nu inloggen maar het systeem niet activeren. Na ruim 5 uur te hebben geprobeerd om maar een werkend systeem te installeren de keuze gemaakt om de machine op kantoor te laten installeren door onze servicedesk. Daar zijn meer juiste installatie media’s beschikbaar en dus ook mogelijk om een goede installatie voor elkaar te krijgen.