MachPanel Knowledgebase

Dedicated PFM Error due to special character

zohaib.shaikh — Tue, 17 Dec 2019 15:11:58 GMT

Summary

This article provide details how to resolve error when creating dedicated PFM from MachPanel in case of of special characters in OU name like ü.

Applies To

This article applies to MachPanel build version 6 and above.

Error Message

Error creating Dedicated PFM : Unable to find assembly 'System.Management.Automation, Version=3.0.0.0, Culture-neutral, PublicKeyToken=31bf33856ad364e35'

In Exchange_ logs the error is:
Dez-17-2019 12:07:00 : Error processing command: Cannot convert 'somedomainürPFM@somedomain.com' to the type 'Microsoft.Exchange.Data.ProxyAddressCollection' required by parameter 'EmailAddresses'. The address 'somedomainürPFM@somedomain.com' is invalid: "somedomainürPFM@somedomain.com" isn't a valid SMTP address. The domain name can't contain spaces and it has to have a prefix and a suffix, such as example.com.

Dez-17-2019 12:07:00 : CommandDetails: set-mailbox -publicfolder -identity "somedomainür PFM" -emailaddresses "somedomainürPFM@somedomain.com" -confirm:$False

Reason

Email addresses "somedomainürPFM@somedomain.com" is the main issue.
This is populated automatically when creating DEDICATED PFM because OU name is somedomainür

ü should be ue
somedomainürPFM => somedomainuerPFM

Resolution

To resolve this, create Shared PFM and assigned only to 1 (concerned) organization. You will get option to type in name of shared PFM where you can enter somedomainuer (as per example used in this KB).

Setting Password Policy in MachPanel

Khurram.hameed — Tue, 17 Mar 2015 04:08:36 GMT

Summary

This article describes how to set up Password Policy in MachPanel for Staff Users as well as throughout the control panel for all password fields like Mailbox or any type of user creation.

Applies To

MachPanel Version 5.2.10 HF2 and above.

Solution

The provider can set up Password Policy in MachPanel to match their Active Directory Password policy so that the password complies with back-end policy before actually attempting to process a request to set password.

We have implemented password policy for staff users set by Provider as default rules to follow for Active Directory User password in Enterprise modules.

The errors generated due to weak password input while creating Mailbox, SharePoint, Lync etc. in job processing can be avoided by setting a matching policy for password in AD and Password Policy for Staff user in Provider settings.

MachPanel will give error if password does not meet requirement before adding single or bulk user/mailbox.

Sample Scenario:

If we set up Password Policy as follows:

Following or similar passwords will fail with error shown below:

passwordabcdefgh

PASSWORDABCDEFGH
password91113156
PASSWORD91113156
Password91113156

Following password or similar (that meet the specified policy) will be accepted and user will be accepted for provisioning:

P@ssw0rd91113156

Powershell error when provisioning a service

mudesira.munir — Tue, 07 May 2013 02:28:41 GMT

Summary

This article provides information how to handle the powershell snap in error when provisioning an Exchange 2013 service.

Applies To

MachPanel v4.x.xx and v5.x.xx

ERROR Message 1:

The Windows PowerShell-Snap-In Microsoft.Exchange.Management.PowerShell.E2010 is trying to load an Exchange 2013 assembly. "C:\Program Files\Microsoft\Exchange Server\V15\bin\Microsoft.Exchange.PowerShell.Configuration.dll"

ERROR MESSAGE 2: (Shows up in windows even viewer)

.NET Runtime version 2.0.50727.4247 - Fatal Execution Engine Error (000007FEF97227FA) (80131506)

Faulting application w3wp.exe, version 7.0.6002.18005, time stamp 0x49e03238, faulting module mscorwks.dll, version 2.0.50727.4247, time stamp 0x5265c61f, exception code 0xc0000005, fault offset 0x00000000006c4b89, process id 0x%9, application start time 0x%10.

ERROR MESSAGE 3: (Shows up in Hyper-V Module)

Error: Error processing command: The term 'New-VM' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Solution

If MachPanel fails to update to the correct version for Lync2013, Exchange2013, Sharepoint2013 use .Net Framework 4.0.

Please follow steps in order to fix the issue:

Open MachSol.MachPanel.Provisioning-Svc.exe.Config on Remote server (normally exchange 2013 mailbox server) under MachPanel Remote Server installation directory.
Replace the code

<       <startup><supportedRuntime version="v2.0.50727"/></startup>
        BY 
<       <startup><supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/></startup>

Replace attached file on remote.
Restart MachPanel Provisioning Service on Remote Server and try creating account again.

Note: Please find "MachSol.MachPanel.Provisioning-Svc.zip" file in attachment.

Exchange Email template values

zohaib.shaikh — Sun, 02 Sep 2012 22:43:08 GMT

Summary

This article provides the information to Update Mailbox template according to environment and replace the platform specific variables in Exchange Email template.

Applies To

Applies to MachPanel v4.3.10 and above.

Solution

1. In order to edit the Exchange Email template navigate to the following path:

Home >> System Configuration >> Emails configuration >> Email Templates

2. Now click on Edit Template under Pakage Info Emails section as shown in the snapshot below:

3. A new tab Edit Template will open. You can insert Company, Customer and Group variables for template group as shown in the snapshot below:

The Email Template variables can be inserted in the template by selecting them from the drop down lists. Following is the list of all variables currently in use in our email template.

Company variables

%CompanyName%: Should be the name of the company.
%CompanyAddress1%: Should be the company address1.
%CompanyAddress2%: Should be the company address2.
%CompanyCity%: Should be the name of city in which the company is located.
%CompanyState%: Should be the name of the company state.
%CompanyZip%: Should be the Zip code of the company’s country.
%CompanyCountry%: Should be the name of the country.
%CompanySalesEmail%: Should be the email address of the company’s Sales team.
%CompanyBillingEmail%: Should be the email address of the company’s Billing.
%CompanySupportEmail%: Should be the email address of the company’s Support team.
%CompanyFax%: Should be the fax of company.
%CompanyURL%: Should be the URL of the company’s website.

Customer Variables

%ClientFirstName%: Should be first name of email recipient.
%ClientLastName%: Should be last name of email recipient.
%ClientID%: Should be the ID of the customer.
%ClientPriEmail%: Should be the primary Email address of the customer.
%ClientSecEmail%: Should be the secondary Email address of the customer.
%ClientCPURL%: Should be the URL of the Control Panel of the customer.
%ClientLoginID%: Control Panel Login ID.
%ClientPassword%: Control Panel password.
%ClientAddress1%: Should be the customer address1.
%ClientAddress2%: Should be the customer address2.
%ClientCity%: Should be the name of city of the customer.
%ClientState%: Should be the name of the customer state.
%ClientZip%: Should be the Zip code of the customer’s country.
%ClientCountry%: Should be the name of the country.
%ClientPhone%: Should be the phone number of the customer.
%ClientMobile%: Should be the mobile number of the customer.
%ClientFax%: Should be the fax of the customer.
OutlookDownloadURL: The provider needs to update this manually for now. We plan to create a form in control panel to feed in such inputs in future builds, probably after build 4.3.14.
EntourageDownloadURL: The provider needs to update this manually for now. We plan to create a form in control panel to feed in such inputs in future builds, probably after build 4.3.14.
"%MXRecordAddress%": The provider needs to update this manually for now. Should be possible to retrieve from Exchange Server settings. We will probably add this enhancement after build 4.3.14.
"%AutoDiscoverRedirectURL%": The provider needs to update this manually for now. Should be possible to retrieve from Exchange Server settings. We will probably add this enhancement after build 4.3.14.
"%OWAURL%": The provider needs to update this manually for now. We plan to create a form in control panel to feed in such inputs in future builds, probably after build 4.3.14.

Group Variables

%MailBoxEmailAddress%: Should be the Mailbox email address.
%MailBoxPassword%: Should be the Mailbox password.
%upnUserName%: Should be the User Principal Name.
%packageName%: Should be the Name of service plan.
%packageType%: Should be the Type of service plan.
%signUpDate%: Should be the Signup date.
%subscriptionID%: Should be the Subscription ID.

Create Portal Failed - Error Creating Portal, [COM Exception] There Is No Such Object On Server

fawad.khan — Wed, 12 Nov 2008 02:21:35 GMT

Summary
Single machine was acting as multiple server roles (e.g. Domain Controller + SQL Database + MachPanel Control Server + DNS + WSS 3.0) and following exception was thrown during Windows SharePoint Services (WSS) 3.0 configuration with MachPanel Provisioning System:
Create Portal Failed.
Detail: Error Creating Portal
Details: [COM Exception]. There is no such Object on the server

Applies To
MachPanel all versions
Hosted SharePoint Extension (SPE)

Solution
The resolution for the above error is available at:
http://kb.machsol.com/Knowledgebase/Article/50063

Important:
Please make sure that for smooth, seamless and successful provisioning by MachPanel the RECOMMENDED SETUP for service preparation should be followed.
http://kb.machsol.com/Knowledgebase/Article/50062

Create Portal Failed - Error Creating Portal, The Server Is Unwilling To Process The Request

fawad.khan — Wed, 12 Nov 2008 01:52:44 GMT

Summary
I encountered the following error while configuring Windows SharePoint Services (WSS) 3.0 through MachPanel.

Create Portal Failed.
Detail: Error Creating Portal
Details: Security Group policy error. The server is unwilling to process the request

Applies To
MachPanel all versions
Hosted SharePoint Extension (SPE)

Cause
Single machine was acting as multiple server roles (e.g. Domain Controller (DC) + SQL Database + MachPanel Control Server + DNS + WSS 3.0)

Solution
The above error can be resolved by separating the Domain Controller (DC). In other words, no software should be installed on DC and it should be separate.

Minimum deployment architecture for successful WSS 3.0 provisioning through MachPanel Provisioning System includes at least three server machines:
For Example:

1. Server 1: Domain Controller (Active Directory Domain + DNS)
2. Server 2: MachPanel Control Server + Database Server
3. Server 3: WSS 3.0 + MachPanel Remote server

Note: Similar resolution steps can be followed for resolving issues regarding Enterprise Extensions i.e. Hosted Exchange Extension (HEE), Hosted Exchange Extension (HEE) for HMC 4.0, BlackBerry Extension (BBE) etc.

Please consult Installation & Service Preparation Guides that explain the details in this regard, available for download at:
http://kb.machsol.com/Downloads/