Archive

Archive for the ‘Group Policy’ Category

safe senders in outlook 2003

July 17, 2008 Leave a comment

Can we automate safe senders in Outlook 2003 via group policy ?

Yes, it is possible to automate safe senders in Outlook 2003 via Group Policy within logon script by doing the following steps:

– create safe senders list ( safesenders.txt ) contain the list of email would you like to add i.e: @fnovento.com ( one per line ) and store it under share folder ( say \\share\safesenders.txt ).

– create logon script to add the following registry entries:

HKCU\Software\Microsoft\Office\11.0\Outlook\Options\Mail\JunkMailImportAppend,1,”REG_DWORD”

HKCU\Software\Microsoft\Office\11.0\Outlook\Options\Mail\JunkMailImportLists,1,”REG_DWORD”

 HKCU\Software\Microsoft\Office\11.0\Outlook\Options\Mail\JunkMailSafeSendersFile,”\\share\safesenders.txt”,”REG_SZ”

Advertisements
Categories: Group Policy

.NET Framework 2.0 Bug

July 9, 2008 1 comment

When you’re deploying .NET Framework 2.0 via Group Policy, there are two options available

  • asssigned 
  • Doing so, the application will be installed on the workstation when reboot. i had tested this and found no problem.

  • published
  • Doing so, the application will be available on users control panel > add remove programs > add new programs. i had tested this and found ERROR.

the ERROR found when you’re publishing the application appears as follow:

MSI (s) (18!84) [14:41:46:857]: Product: Microsoft .NET Framework 2.0 — 1: ALLUSERS property is not 1 – this MSM cannot be used for a per-user or fallback-to-per-user install 2:

if you want to find out the root cause for this you may try to access http://blogs.msdn.com/astebner/archive/2007/01/30/resolving-net-framework-2-0-setup-error-related-to-the-allusers-property.aspx

if you wanna to find microsoft official resources for this you may try to access http://msdn.microsoft.com/en-us/library/aa480237.aspx

Categories: Group Policy

Adobe Reader Bugs

July 7, 2008 Leave a comment

Even though Adobe Reader 8/8.1/8.1.2/9 released with no notification about bugs, but i found a critical bugs when deploying the package with Group Policy. Sometimes you want the users to be able to install Adobe Reader package from Control Panel > Add Remove Programs. This can be achieve by publish the package on Software Installation ( User Configurations ).

The problem may occured if you’re logon as authenticated users ( with no admin privillage ) and try to install the Adobe package from Control Panel > Add Remove Programs > Add New Programs where you will receive this ERROR.

Adobe Reader 8.1.2 requires Internet Explorer 6.0 or greater. Please visit www.microsoft.com to upgrade Internet Explorer. …

Eventhough you have Internet Explorer 7 installed on your PC, the ERROR still appeared. This problem occured on Adobe Reader 8/8.1/8.1.2/9 where i call it as a bug.

Here’s the thing that you should do:

  1. Download Adobe Reader package from Adobe Official website and extract the package to msi.  The package itself was build with Nosso technology so you’re gonna have to extract it with the following command ( AdbeRdr90_en_US.exe -nos_ne )
  2. It will create Abcpy.ini, AcroRead.msi,Data1.cab,Setup.exe,setup.ini on the c:\documents and settings\<<currentuser>>\local settings\application data\adobe\reader 9.0\Setup Files
  3. copy all files to share folder
  4. download orca ( free msi editor )
  5. edit AcroRead.msi with orca. Delete the following table.                                                               
    Property – IsMinIE_Message
    CustomAction – IsMinIE                                                             
    then save
  6. your package ( AcroRead.msi ) are ready to be publish with Group Policy on Software Installation – User Configuration
Categories: Group Policy