Windows Vista Forums
Vista Forums Home Join Vista Forums Donate Vista Tutorials Tags

Welcome to Vista Forums we are your forum to discuss Windows Vista x64 and x86 systems. Whether you need help or just want to post an idea you have on Vista, this is the forum for you.
Register at Vista forums...the world biggest Windows Vista resource Join Vista Forums Now

Go Back   Vista Forums > Microsoft Technical Newsgroups > PowerShell

Exchange 2007 Administration through 32-bit windows service.

Update your Vista Drivers Update Your Drivers Now!!
Closed Thread
 
Thread Tools Display Modes
Old 08-06-2007   #1 (permalink)
RD
Guest


 

Exchange 2007 Administration through 32-bit windows service.

I've a 32-bit compiled windows service which carries out many Exchange
administration and monitoring tasks through VBScripts and C++ utilities using
CDOEXM. I just started making changes for Exchange 2007 using powershell
because I thought that is the correct path. Well, I ran in to a problem where
loading of Microsoft.Exchange.Management.PowerShell.Admin
snap-in fails with the error - "No Windows PowerShell Snap-ins are
available for version 1"
("http://blogs.msdn.com/mstehle/archive/2007/01/24/kb-preview-error-no-windows-powershell-snap-ins-when-loading-exchange-powershell-snap-in.aspx").

I'm wondering what are my options here if I can't recompile my service
program as 64-bit application. If I write .Net managed code utility (*.exe
from *.cs) 32-bit/64-bit(?) using Exchange assembly, will I be able to invoke
through win32
service?

I came across API Wow64DisableWow64FsRedirection() and wondering if 32-bit
cmd.exe has an option to invoke 64-bit Powershell.exe which in turn can load
Exchange assembly.

Note: I also have ADSI programs which runs fine on 64-bit Windows 2003 with
Exchange 2007. Any limitation on using ADSI in win32 app?

My System SpecsSystem Spec
Old 08-08-2007   #2 (permalink)
RD
Guest


 

RE: Exchange 2007 Administration through 32-bit windows service.

Looks like there is no way for a 32-bit cmd.exe to invoke 64-bit
powershell.exe. So I copied
%systemroot%\system32\windowspowershell\v1.0\powershell.exe to
%MyApplicationInstallPath%\bin folder and then invoked
%MyApplicationInstallPath%\bin\powershell.exe from my script and it worked.
It successfully loaded Exchange admin assembly. Other than maintenance
(service packs) issue, this should work. Has anyone tried this?

I think Wow64*Wow64FsRedirection() APIs are needed only if you happen to
invoke a system utility from your own 32-bit application.

"RD" wrote:

> I've a 32-bit compiled windows service which carries out many Exchange
> administration and monitoring tasks through VBScripts and C++ utilities using
> CDOEXM. I just started making changes for Exchange 2007 using powershell
> because I thought that is the correct path. Well, I ran in to a problem where
> loading of Microsoft.Exchange.Management.PowerShell.Admin
> snap-in fails with the error - "No Windows PowerShell Snap-ins are
> available for version 1"
> ("http://blogs.msdn.com/mstehle/archive/2007/01/24/kb-preview-error-no-windows-powershell-snap-ins-when-loading-exchange-powershell-snap-in.aspx").
>
> I'm wondering what are my options here if I can't recompile my service
> program as 64-bit application. If I write .Net managed code utility (*.exe
> from *.cs) 32-bit/64-bit(?) using Exchange assembly, will I be able to invoke
> through win32
> service?
>
> I came across API Wow64DisableWow64FsRedirection() and wondering if 32-bit
> cmd.exe has an option to invoke 64-bit Powershell.exe which in turn can load
> Exchange assembly.
>
> Note: I also have ADSI programs which runs fine on 64-bit Windows 2003 with
> Exchange 2007. Any limitation on using ADSI in win32 app?

My System SpecsSystem Spec
Old 08-08-2007   #3 (permalink)
Oisin Grehan
Guest


 

Re: Exchange 2007 Administration through 32-bit windows service.

On Aug 8, 4:54 pm, RD <R...@discussions.microsoft.com> wrote:
> Looks like there is no way for a 32-bit cmd.exe to invoke 64-bit
> powershell.exe. So I copied
> %systemroot%\system32\windowspowershell\v1.0\powershell.exe to
> %MyApplicationInstallPath%\bin folder and then invoked
> %MyApplicationInstallPath%\bin\powershell.exe from my script and it worked.
> It successfully loaded Exchange admin assembly. Other than maintenance
> (service packs) issue, this should work. Has anyone tried this?
>
> I think Wow64*Wow64FsRedirection() APIs are needed only if you happen to
> invoke a system utility from your own 32-bit application.
>
>
>
> "RD" wrote:
> > I've a 32-bit compiled windows service which carries out many Exchange
> > administration and monitoring tasks through VBScripts and C++ utilities using
> > CDOEXM. I just started making changes for Exchange 2007 using powershell
> > because I thought that is the correct path. Well, I ran in to a problem where
> > loading of Microsoft.Exchange.Management.PowerShell.Admin
> > snap-in fails with the error - "No Windows PowerShell Snap-ins are
> > available for version 1"
> > ("http://blogs.msdn.com/mstehle/archive/2007/01/24/kb-preview-error-no-...").

>
> > I'm wondering what are my options here if I can't recompile my service
> > program as 64-bit application. If I write .Net managed code utility (*.exe
> > from *.cs) 32-bit/64-bit(?) using Exchange assembly, will I be able to invoke
> > through win32
> > service?

>
> > I came across API Wow64DisableWow64FsRedirection() and wondering if 32-bit
> > cmd.exe has an option to invoke 64-bit Powershell.exe which in turn can load
> > Exchange assembly.

>
> > Note: I also have ADSI programs which runs fine on 64-bit Windows 2003 with
> > Exchange 2007. Any limitation on using ADSI in win32 app?- Hide quoted text -

>
> - Show quoted text -


Any reason why you copy the 32bit posh into your appdir? why not
invoke it directly from the system32\p.. path?

If you have a good reason for placing it under your appdir, perhaps
you could sidestep the servicepack/update issue by creating a symlink
(junction) under your bin to the v1.0 directory.

- Oisin

My System SpecsSystem Spec
Closed Thread
Update your Vista Drivers Update Your Drivers Now!!

Thread Tools
Display Modes



Similar Threads
Thread Thread Starter Forum Replies Last Post
RSAT Exchange tabs (Remote Server Administration Tools) SirOssis Vista account administration 0 04-10-2008 09:25 AM
Exchange Management Tool and Administration of group directors Luis Barroso Vista installation & setup 0 08-17-2007 02:24 PM
Stop the smtp service on an Exchange 2007 server? SuneR PowerShell 11 07-19-2007 08:24 AM
Microsoft Readies IT Customers for Windows Vista, the 2007 Office System, Microsoft Exchange Server 2007 z3r010 Vista News 0 11-14-2006 07:03 PM
Microsoft Readies IT Customers for Windows Vista, the 2007 Office System, Microsoft Exchange Server 2007 z3r010 Vista News 0 11-14-2006 11:04 AM


Vistax64.com is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows Vista", the Start Orb, and related materials are trademarks of Microsoft Corp.
© Designer Media 2005-2008

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51