Regenerate Self Signed Certificate Exchange 2007 / 2010


To Regenerate the Self Signed Certificate for Exchange this might be a bit tricky.

Open the Exchange Power Shell.

For SBS Server the names of the certificates it’s sites, you need to get the certificate name to be able to regenerate.

Get-ExchangeCertificate -domain “Sites” | fl

Note the ThumbPrint Value.

Generate the New Certificates

Get-ExchangeCertificate -thumbprint “D1B3829EC891FD53C1F87FF8359FFBEE8E3FB412” | New-ExchangeCertificate

Answer A to All

Enable Exchange Certificate for all the services

Enable-ExchangeCertificate -thumbprint “D1B3829EC891FD53C1F87FF8359FFBEE8E3FB412” -services IIS

After the certificate renew, you might receive on the server and the workstation

“This Ca Root Certificate Is Not Trusted. To enable Trust, Install This Certificate In The Trusted Root Certification Authorities Store”

Go to the Default Web Site in IIS and remove the Self Signed Cert **** The old one **** Check the certificate Date. Right click the Default Web Site, Directory Security, Server Certificate, Next, and Remove the cert.

Open Certificates in MMC. Go to Run, MMC. File Add Remove Snap In, Add Certificates; Computer Account; Local Computer and Click OK.

Copy the new cert to the Trusted Root Certification Authorities Certificates.

Go back to the Default Website in IIS, Properties, Diretory Security, Server Certificate. Assign an existing certificate and choose the new cert that was created.

Open a prompt : IISRESET

Sage CRM 7.1 Installation Tips – Avoid creating the database during the install – Tips in a Clustering Install


If you want to install Sage CRM to another Server and skip the creation of the database (if the CRM database already exist and in use in production the Setup will failed and Rollback).

This can be usefull if you want to transfer the CRM to another server or deploy a new CRM install in a Clustering Mode.

From a command prompt (cmd.exe) start the CRM Setup setup.exe with the option nodb

setup.exe nodb

Have Fun deploying several Node !

Service Pack :

“There’s no need for the nodb option for Service packs. Yes service packs might update the metadata, but it doesn’t affect the database if you re-run the same patch more than once. ” From Sage Support Level 3

Enterprise Activation on Blackberry Device Software 4 – 5 – 6 – 7

The BlackBerry smartphone user can start the wireless activation process after receiving the password by completing the following steps:

For BlackBerry Device Software 4.1 to 5.0:

  1. On the BlackBerry smartphone, click Options > Advanced Options > Enterprise Activation.
  2. Enter the email address associated with the BlackBerry smartphone user account in the Emailfield.
  3. Enter the Activation Password provided by the administrator.
  4. Press the Menu key and select Activate.

For BlackBerry 6 to 7:

  1. On the BlackBerry smartphone, click Options > Device > Advanced System Settings >Enterprise Activation.
  2. Enter the email address associated with the BlackBerry smartphone user account in the Emailfield.
  3. Enter the Activation Password provided by the administrator.
  4. Press the Menu key and select Activate.

LikeWise Ubuntu Login (including xRdp)

Adding users to sudoers

We will be editing /etc/sudoers file for this:
sudo gedit /etc/sudoers

Look for the following line:
# Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL

Add a lines as explained below:

If you have set default domain
username ALL=(ALL) ALL # Allow specific account to sudo
domain^admins ALL=(ALL) # Allow admin group
domain^users ALL=(ALL) ALL # Allow all domain users

if you are not using default domain then you have to include the domain name:
%mydomain\yourusername ALL=(ALL) ALL
%mydomain\domain^admins ALL=(ALL) ALL
%mydomain\domain^users ALL=(ALL) ALL

Add domain username to login screen user list

sudo gedit /etc/gdm/custom.conf
Add the greeter part at the end of the file. Add your domain username to include section and any other you want to exclude.


Reference :

Sage CRM 7 Fileit issue Return a script error in the Page (Internet Explorer Error)


In Outlook even if it’s 2010, 2007 and you use the Sage CRM Outlook Plug In : File it, you might receive an error look like :


To fix this issue, check the security profile in CRM for the users, in my case my issue was related to the Opportunity Security was set to “No Access”. I set a value of “View” and Magic, the user is able to do the File It.



Export all SMTP address into a CSV from Exchange 2007 and 2010 (PowerShell)

In the Exchange Power Shell :

Get-Mailbox -ResultSize Unlimited |Select-Object DisplayName,ServerName,PrimarySmtpAddress, @{Name=“EmailAddresses”;Expression={$_.EmailAddresses |Where-Object {$_.PrefixString -ceq “smtp”} | ForEach-Object {$_.SmtpAddress}}} | Export-Csv  c:smtp.csv –NoTypeInformation

The file smtp.csv will be located in c:

You might want to change the path.


Sage CRM 7.0, 7.1 and Complete Sage Accpac Integration


For freak security users like me 🙂 This is the required open port if you deploy on a Web Server Sage CRM 7.x and a complete Sage Accpac Integration.


Sage CRM=> Default Port 80 and 443, depending on what port you are using for HTTP and HTTPs.
Sage Accpac Web Deploy (Open OE/AR windows from CRM) => Default Port 9000-9180 and can be expanded during web deployment setup. Accpac opens one port per UI opened.

Crystal Web Reporting (Print OE from CRM) => default port 80.

Sage Accpac Portal => whatever HTTP you are using, plus 10015 (server) and 10020 (AJP).


More information after the break




Sage Accpac ERP 300 or ERP 200 – 100 – 500 or Version 6.0 5.6 5.5


If you have a customer and they want to implement SQL replication on a Sage Accpac Database (please check the title for all the possible version, change doesn’t change their product name often :S )

They might received an error the table A4WCHARORDER cannot be added to the replication because it doesn’t have a PK (Primary Key). All the table can be replicated except the A4WCHARORDER.

According to Sage Senior support Team :

Sage 300 generates this table A4WCHARORDER if it doesn’t exist. So this is not important to backup.
To clarify, it is still actively used to “figure how the database collation sort between min and max characters”.

Sage support “One Way” Replication not Both Way….. This is by design…