The registry key you added was in the Wow6432Node part of the registry... try adding the same key to the 64-bit Software registry hive and see what happens.
On Wed, Sep 3, 2014 at 12:00 PM, Wilbers, Scott <[email protected]> wrote: > I can import ConfigMgr module with PowerShell (x86)…but R2 should > support either. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Daniel Ratliff > *Sent:* Wednesday, September 3, 2014 11:47 AM > *To:* [email protected] > *Subject:* [mssms] RE: Console Issues on WIndows 8.1 x64 > > > > Just knocking the two easy ones off first. > > > > Did you use PowerShell x86 when you connected? > > > > Did you run as administrator? > > > > *Daniel Ratliff* > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Wilbers, Scott > *Sent:* Wednesday, September 03, 2014 11:11 AM > *To:* '[email protected]' > *Subject:* [mssms] Console Issues on WIndows 8.1 x64 > > > > I rebuilt my laptop with Windows 8.1 x64. When I installed the console I > was unable to connect to my site (R2 is installed). I found this > http://sccmfaq.wordpress.com/2013/10/22/sccm-2012-r2-console-on-windows-8-1-cant-connect-to-sms-provider/ > and added the key. I am now able to connect to the console, but when I try > to connect via PowerShell I get this error: > > > > Import-Module : No query processors registered. > > At line:1 char:1 > > + Import-Module 'C:\Program Files (x86)\Microsoft Configuration > Manager\AdminConso ... > > + > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > + CategoryInfo : InvalidOperation: (:) [Import-Module], > TypeLoadException > > + FullyQualifiedErrorId : > NewDriveProviderException,Microsoft.PowerShell.Commands.ImportModuleCommand > > > > CD : Cannot find drive. A drive with the name 'CBC' does not exist. > > At line:1 char:116 > > + ... Manager.psd1'; CD CBC: | Invoke-Expression > > + ~~~~~~~ > > + CategoryInfo : ObjectNotFound: (CBC:String) [Set-Location], > DriveNotFoundException > > + FullyQualifiedErrorId : > DriveNotFound,Microsoft.PowerShell.Commands.SetLocationCommand > > > > > > Anyone seen this before or have any ideas? > > *------------------------------------------* > > *Scott Wilbers* > > *Network Administrator* > > Central Technology Services > > 2100 Stewart Drive > > Jefferson City, MO 65109 > > Phone: (573) 634-5600 ext 6420 > > Fax: (573) 681-6301 > > <mailto:[email protected] <[email protected]>*>* > > > > > ************************************************************************************************** > Note: > The information contained in this message may be privileged and > confidential and > protected from disclosure. If the reader of this message is not the > intended > recipient, or an employee or agent responsible for delivering this message > to > the intended recipient, you are hereby notified that any dissemination, > distribution or copying of this communication is strictly prohibited. If > you > have received this communication in error, please notify us immediately > by > replying to the message and deleting it from your computer. > > ************************************************************************************************** > > > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information. > > > > > ************************************************************************************************** > > Note: > The information contained in this message may be privileged and > confidential and > protected from disclosure. If the reader of this message is not the > intended > recipient, or an employee or agent responsible for delivering this message > to > the intended recipient, you are hereby notified that any dissemination, > distribution or copying of this communication is strictly prohibited. If > you > have received this communication in error, please notify us immediately > by > replying to the message and deleting it from your computer. > > ************************************************************************************************** > > >
