# Can't add Snapin **URL:** \ **Category:** PowerShell Help\ **Created:** [February 17, 2022, 10:18am UTC](https://forums.powershell.org/t/cant-add-snapin/18606 "2022-02-17T10:18:06Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![dady](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/dady/32/1710_2.png) [@dady](https://forums.powershell.org/u/dady)\ **Post date:** [February 17, 2022, 10:18am UTC](https://forums.powershell.org/t/cant-add-snapin/18606/1 "2022-02-17T10:18:07Z")
Hi all, I have a new computer and i can’t run the a script i use to run on my old one. I get an error message > PS F:\> Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn; > Add-PSSnapin : No snap-ins have been registered for Windows PowerShell version 5. > At line:1 char:1 > > - Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn; > - > > ```auto > + CategoryInfo : InvalidArgument: (Microsoft.Excha...werShell.SnapIn:String) [Add-PSSnapin], PSArgumentException > + FullyQualifiedErrorId : AddPSSnapInRead,Microsoft.PowerShell.Commands.AddPSSnapinCommand > > ``` I have searched everywhere with no luck. I hope i will find here the solution. I already set the "ExecutionPolicy " to “RemoteSigned” Here are the “Old” computer details: Win 10 pro version 1809 Build 17763.1577 PS version 5.1.17763.1490 New computer details: Win 10 pro version 20H2 build 19042.1466 PS version 5.1.19041.1320 Any help will be appreciated. ---
**Author:** ![kvprasoon](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/kvprasoon/32/4449_2.png) [@kvprasoon](https://forums.powershell.org/u/kvprasoon)\ **Post date:** [February 17, 2022, 4:28pm UTC](https://forums.powershell.org/t/cant-add-snapin/18606/2 "2022-02-17T16:28:13Z")
IMO, you gotta have the exchange management tools installed. That snapin is not by default available in the OS\> ---
**Author:** ![Olaf](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/olaf/32/992_2.png) [@Olaf](https://forums.powershell.org/u/Olaf)\ **Post date:** [February 17, 2022, 5:12pm UTC](https://forums.powershell.org/t/cant-add-snapin/18606/3 "2022-02-17T17:12:11Z")
What problem do you try to solve actually? We actually do not use snapins anymore. On an on premisses Exchange server you can launch an Exchange management shell with `launchems`. If you want to manage an Exchange server remotely you should use implicit remoting to use the Exchange cmdlets. > **[Connect to Exchange servers using remote PowerShell](https://docs.microsoft.com/en-us/powershell/exchange/connect-to-exchange-servers-using-remote-powershell?view=exchange-ps)** > > Use Windows PowerShell on a local computer to connect to an Exchange Server. ---
**Author:** ![krzydoug](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/krzydoug/32/1008_2.png) [@krzydoug](https://forums.powershell.org/u/krzydoug)\ **Post date:** [February 17, 2022, 6:02pm UTC](https://forums.powershell.org/t/cant-add-snapin/18606/4 "2022-02-17T18:02:01Z")
Implicit remoting is great. If you really want the old snappin you’ll have to install the exchange management tools for the specific version. I believe you can still access older exchange with newer tools. There is also an unsupported remote exchange setup script you can find on the internet. I believe I even posted it as an answer on this very forum, I’ll try to find it. ---
**Author:** ![krzydoug](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/krzydoug/32/1008_2.png) [@krzydoug](https://forums.powershell.org/u/krzydoug)\ **Post date:** [February 17, 2022, 6:26pm UTC](https://forums.powershell.org/t/cant-add-snapin/18606/5 "2022-02-17T18:26:44Z")
Check my answer on this post > [@Running Get-ExchangeCertificate using a remote session.](https://forums.powershell.org/t/running-get-exchangecertificate-using-a-remote-session/15035): > > I am writing a PowerShell script to take an automated backup of the Exchange environment. In the process of doing that i need to run “Get-ExchangeCertificate | select Thumbprint, Services, CertificateDomains” and get “certificate domains” and other fields from an Exchange 2016 Environment. If I run this command via the “Exchange management shell” the command works fine and displays the “certificate domains”. But If I were run PowerShell and connect to the on-premises environment (New-PSSessi… **Edit** Looks like that script was on Technet. Thank goodness for the internet archive! Archived page > **[Office Import-ModuleExchange](https://web.archive.org/web/20210126095021/https://gallery.technet.microsoft.com/Import-ModuleExchange-010da141)** > > Imports a fully functional Exchange Module for Exchange 2010, as if using the Exchange Shell. > \- Full Deserialization of objects > \- Enables use of all cmdlets > \- Needs no prior local installation of Exchange Management Tools Direct link to ps1 [https://web.archive.org/web/20200328155702/https://gallery.technet.microsoft.com/Import-ModuleExchange-010da141/file/134284/3/Import-ModuleExchange.ps1](https://web.archive.org/web/20200328155702/https://gallery.technet.microsoft.com/Import-ModuleExchange-010da141/file/134284/3/Import-ModuleExchange.ps1) ---
**Author:** ![dotnVo](https://avatars.discourse-cdn.com/v4/letter/d/4af34b/32.png) [@dotnVo](https://forums.powershell.org/u/dotnVo)\ **Post date:** [May 16, 2024, 8:19pm UTC](https://forums.powershell.org/t/cant-add-snapin/18606/6 "2024-05-16T20:19:32Z")