Product, version and build: PowerShell Studio 2016 5.2.121
32 or 64 bit version of product: 64 bit
Operating system: Win 10
32 or 64 bit OS: 64 bit
DO NOT POST SUBSCRIPTIONS, KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM
I'm trying to load the Exchange 2013 cmdlets into PowerShell Studio 2016 with no luck. I used the export cache application on one of our Exchange servers and imported the cache (as per the two part instructions.) I can select our Exchange server as the remote machine and it populates modules and some snapins but not the Exchange snapins. I'm assuming that I did something wrong in the export/import cache process? I attached the cache file I took from our Exchange server. Any help on this would be greatly appreciated.
Thank you,
Justin
Can't get Exchange 2013 Cmdlets to work with PrimalSense
Forum rules
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Can't get Exchange 2013 Cmdlets to work with PrimalSense
- Attachments
-
- NAHQSMX11.zip
- (280.05 KiB) Downloaded 178 times
Re: Can't get Exchange 2013 Cmdlets to work with PrimalSense
The Exchange snapins have been notorious for causing issues during caching.
Try the following steps and see if this resolves the issue:
1. Copy the following folders to the server (depending on Posh version):
For V2:
C:\ProgramData\SAPIEN\PresetCache 2016\ModuleCacheV2
For V3 or V4:
C:\ProgramData\SAPIEN\PresetCache 2016\ModuleCacheV3
For V5:
C:\ProgramData\SAPIEN\PresetCache 2016\ModuleCacheV5
2. Run the Export Cache again.
3. Re-import the CacheExport file.
David
Try the following steps and see if this resolves the issue:
1. Copy the following folders to the server (depending on Posh version):
For V2:
C:\ProgramData\SAPIEN\PresetCache 2016\ModuleCacheV2
For V3 or V4:
C:\ProgramData\SAPIEN\PresetCache 2016\ModuleCacheV3
For V5:
C:\ProgramData\SAPIEN\PresetCache 2016\ModuleCacheV5
2. Run the Export Cache again.
3. Re-import the CacheExport file.
David
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: Can't get Exchange 2013 Cmdlets to work with PrimalSense
Thanks David,
So I'm seeing a bunch of Microsoft.Exchange.Management.Powershell... files in the ModuleCacheV3 folder. We are running V4 on the Exchange servers. They all seem to be for 2010 and are a bit older, obviously not something that I just cached yesterday. These seem to be in plain text and I can read the cmdlets in Notepad.
Refreshing the Cache and re-importing the cache from the Exchange server, following your instructions, didn't seem to help.
So I'm seeing a bunch of Microsoft.Exchange.Management.Powershell... files in the ModuleCacheV3 folder. We are running V4 on the Exchange servers. They all seem to be for 2010 and are a bit older, obviously not something that I just cached yesterday. These seem to be in plain text and I can read the cmdlets in Notepad.
Refreshing the Cache and re-importing the cache from the Exchange server, following your instructions, didn't seem to help.
Re: Can't get Exchange 2013 Cmdlets to work with PrimalSense
I believe we updated the preset-cache in the new build (5.2.122). If you let me know the exact version number of your Exchange modules, I can check if we have the files and attach them to this topic. In the case were we don't have the cache files, I can send you a script that that will generate the files for you.
Note: In an upcoming service release, we are going to allow users to create cache profiles for machines by selecting the modules from the preset cache, without having to run the export cache tool.
David
Note: In an upcoming service release, we are going to allow users to create cache profiles for machines by selecting the modules from the preset cache, without having to run the export cache tool.
David
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: Can't get Exchange 2013 Cmdlets to work with PrimalSense
Thanks for the response, these are the only numbers I could find:
In the module description ExchClientVer=15.0.1156.6
Module Version 1.0
Even using the EMS PowerShell is using implicit remoting and importing the module as the FQDN of the Exchange server. Not sure how I would be able to get the exact version number of the module?
In the module description ExchClientVer=15.0.1156.6
Module Version 1.0
Even using the EMS PowerShell is using implicit remoting and importing the module as the FQDN of the Exchange server. Not sure how I would be able to get the exact version number of the module?
Re: Can't get Exchange 2013 Cmdlets to work with PrimalSense
Here is a quick way of getting a module's version:
Here are the latest cache files that we have:
Just copy them into the presetcache folder on the server:
C:\ProgramData\SAPIEN\PresetCache 2016\ModuleCacheV2
C:\ProgramData\SAPIEN\PresetCache 2016\ModuleCacheV3
C:\ProgramData\SAPIEN\PresetCache 2016\ModuleCacheV5
Then run the cache export again.
David
- (Get-Module ModuleName -ListAvailable).Version
Just copy them into the presetcache folder on the server:
C:\ProgramData\SAPIEN\PresetCache 2016\ModuleCacheV2
C:\ProgramData\SAPIEN\PresetCache 2016\ModuleCacheV3
C:\ProgramData\SAPIEN\PresetCache 2016\ModuleCacheV5
Then run the cache export again.
David
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: Can't get Exchange 2013 Cmdlets to work with PrimalSense
You are welcome I'm glad I was able to help.
David
David
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.