Centralized signature in Office 365

If you import it with exact path then it should work.. For example..

Import-module "C:\Temp\EmailSignature\SetOSCEXOEmailSignature1.psm1"

Select allOpen in new window

Can you post the screenshot of the error?

Hi,
i tried it but it appear another error.
i attached image.

Hope you have copied the PSM! file at C:\Temp\EmailSignature

Can you translate the error to English? or Just copy paste the complete error here?

For sure! I copied the right file with psm1 extension!
This is tralnstion about it: Import-Module: Could not load module 'C: \ temp \ EmailSignature \ SetOSCEX
OEmailSignature.psd1 'specified. No valid module file found in the modules directory.
At line: 1 car: 14
+ Import-module <<<< C: \ temp \ EmailSignature \ SetOSCEXOEmailSignature.psd1
     + CategoryInfo: ResourceUnavailable: (C: \ temp \ EmailSi ... lSignatu
    re.psd1: String) [Import-Module], FileNotFoundException
     + FullyQualifiedErrorId: Modules_ModuleNotFound, Microsoft.PowerShell.Comm
    ands.ImportModuleCommand

The I try to import-module with the .psd1 exstension bt appear another message:
Import-Module : Could not import the module ' C: \ temp \ EmailSignature \ en-US \ S
etOSCEXOEmailSignature.psd1 'because its manifest contains one or more me
mbri invalid . The members of the manifest are valid ' ModuleToProcess ' , ' NestedMo
dules ' , ' guid ' , ' Author ' , ' CompanyName ' , ' Copyright ' , ' ModuleVersion ' , ' Descrip
tion ' , ' PowerShellVersion ' , ' PowerShellHostName ' , ' PowerShellHostVersion ' , ' CLR
Version ' , ' DotNetFrameworkVersion ' , ' ProcessorArchitecture ' , ' RequiredModules ' ,
 ' TypesToProcess ' , ' FormatsToProcess ' , ' ScriptsToProcess ' , ' PrivateData ' , ' Requ
iredAssemblies ' , ' ModuleList ' , ' FileList ' , ' FunctionsToExport ' , ' VariablesToExp
ort ' , ' AliasesToExport ' , ' CmdletsToExport ' . Remove the invalid members ( ' Exi
stingTextSignature ' , ' CannotFindExWebSvcVariable ' , ' SaveExWebSvcVariable ' , ' Ever
dExWebSvcVariable ' , ' ExistingHtmlSignature ' , ' EstablishConnection ' , ' InstallExW
ebSvcModule ' , ' SetOWASignature ' , ' GetOWAUserOptions ' , ' RequireConnection ' ) , here
ndi try to import the module .
At line: 1 car : 14
+ Import-module <<<< C: \ temp \ EmailSignature \ en-US \ SetOSCEXOEmailSignature.psd1
    + CategoryInfo : InvalidData : (C: \ temp \ EmailSi ... lSignature.psd1 :
   String) [ Import-Module ] , InvalidOperationException
    + FullyQualifiedErrorId : Modules_InvalidManifestMember , Microsoft.PowerShe
   ll.Commands.ImportModuleCommand

Regards,

Okie I cannot test it now.. You can try copying the files to PowerShell modules folder and then import it..

To do that.. Trype $env:PSModulePath in powershell and note down the path displayed in result.

Ideally you can find the following path's in result..

C:\Users\<UserName>\Documents\WindowsPowerShell\Module

and

C:\Windows\system32\WindowsPowerShell\v1.0\Modules\

Now  extract the content of SetOSCEXOEmailSignature.zip to any one of the PS module path.. It should create SetOSCEXOEmailSignature folder inside the module path and there will be SetOSCEXOEmailSignature.psm1 inside it..

Once you complete, Close and re-open the powershell and run following command to import the module..

Import-Module SetOSCEXOEmailSignature

Select allOpen in new window

I try to do it but it appeared this error:

Import-Module: Could not load module 'SetOSCEXOEmailSignature' specif
ied. No valid module file found in the modules directory.
At line: 1 car: 14
+ Import-Module <<<< SetOSCEXOEmailSignature
     + CategoryInfo: ResourceUnavailable: (SetOSCEXOEmailSignature St
    ring) [Import-Module], FileNotFoundException
     + FullyQualifiedErrorId: Modules_ModuleNotFound, Microsoft.PowerShell.Comm
    ands.ImportModuleCommand

Could you please post the results of the following commands? Also make sure you are running the commands with a admin account which has sufficient permission on that computer.

Get-ExecutionPolicy
Get-Module -ListAvailable
$env:psmodulepath -split ";" | GCI | ?{$_.Psiscontainer}

Select allOpen in new window

PS C:\Windows\system32> Get-ExecutionPolicy
Unrestricted
PS C:\Windows\system32> Get-Module -ListAvailable

ModuleType Name                      ExportedCommands
---------- ----                      ----------------
Manifest   AppLocker                 {}
Manifest   BitsTransfer              {}
Manifest   MSOnline                  {}
Manifest   MSOnlineExtended          {}
Manifest   PSDiagnostics             {}
Manifest   TroubleshootingPack       {}


PS C:\Windows\system32> $env:psmodulepath -split ";" | GCI | ?{$_.Psiscontainer}



    Directory: C:\Users\ddileo\Documents\WindowsPowerShell\Modules


Mode                LastWriteTime     Length Name
----                -------------     ------ ----
d----        27/11/2013     14.46            Documentation_files
d----        27/11/2013     14.46            en-US


    Directory: C:\Windows\system32\WindowsPowerShell\v1.0\Modules


Mode                LastWriteTime     Length Name
----                -------------     ------ ----
d---s        14/07/2009     13.19            AppLocker
d---s        16/10/2013     20.22            BitsTransfer
d----        27/11/2013     14.46            Documentation_files
d----        27/11/2013     14.46            en-US
d----        22/11/2013      9.59            MSOnline
d----        22/11/2013      9.59            MSOnlineExtended
d----        14/07/2009      7.32            PSDiagnostics
d----        14/07/2009     12.52            TroubleshootingPack

I didn't see the folder SetOSCEXOEmailSignature in the module path from result? Where did you extract the module files?

Hi,
i solved the issue with GUI because the editor for transport rules is even an editor html.

Regards,

I've requested that this question be closed as follows:

Accepted answer: 0 points for r3helpdesk's comment #a39715942

for the following reason:

i solved the issue with GUI because the editor for transport rules is even an editor html.

Could please explain the solution in detail and close the question? So that it will be helpful for others who look to resolve similar issue?..

This is the right way to create a centralized signature without use Powershell but simply using GUI with html tags:

http://help.outlook.com/en-us/140/ff852816.aspx

For me it solved.

Regards,