Powershell Windows Server 2008 R2 - SP 2007

Hi
I am working with Windows server 2008 R2, which has windows powershell, but I want to set up/use SP PowerShell
any ideas how I go about doing this?

See this similar thread - How
to install Sharepoint powershell to MOSS 2007
Please 'propose as answer' if it helped you, also 'vote helpful' if you like this reply.

Similar Messages

Unable to install SAP B1 on Windows server 2008 R2

Hi
I am unable to install the SAP Business one 2007 B PL00 on Windows server 2008 R2.
Environment is set as following :
1. SQL SERVER 2008 Installed on Server A
2. SAP B1 to be installed on Server B
3 Both servers are in domain
4.Firewall is off
5. ODBC Connection is tested Successfully
6 Port is also seem to be ok.
But after Installing server tool, when trying to install the Server , in server type nothing is displayed.
I also checked the connecting SQL server from the instance .
Please help is this is related to compatibility of Windows server 2008 R2 with 2007 B or so .
Thanks & Regards
RP

Windows server 2008 R2 is not a supported OS for a lower 2007 version. You need to install a higher version.
Hi Gordon ,
It means I have to install SAP 2007 B PL10 afterwards upgrade it to the latest patch level .
But searching in the forms , i have seen some bopdy installed the SAP 2007 B PL15 on Windows server 2008 R2.
Thanks in advance
Regards
RP

The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine (Windows Server 2008 R2 (64) vs MS Office 2007)

We just have switched our local server from 32-bit to 64-bit machine and now we have Windows Server 2008 R2 Service
Pack 1 with MS Office 2007. On server we are running an application in ASP.Net 3.5 using visual studio
2008. All users have 32-bit windows 7 and MS Office 2007.
when user tries to import data from Excel to Database (SQL Server 2005), error comes as
"microsoft.ace.oledb.12.0 provider is not registered on local machine".
I have tried a solution by installing Access Database Engine 2007 Office System Driver on the Server, but the error
was same. Now what should I do to resolve this problem??? Should we install Office 2010 64-bit on the Server or is there any other solution???

Hi,
Thanks for your posting.
the file can be made in excel 2007, try to install:2007 Office System Driver: Data Connectivity Components
http://www.microsoft.com/en-us/download/details.aspx?id=23734
Regards.
Vivian Wang
TechNet Community Support

PowerShell Script running Excel won't run on Windows Server 2008 R2

I have a script that creates a report of a single example of each warning or error in the Windows Event log, for each server in a list of servers,with the number of times that error has occurred in the last week on each server. It creates this report in
Excel. I have this script running automated through Task Scheduler for one client on Windows 7 and it's working perfectly. I have another client that I am attempting to run this script automated on a server running Windows Server 2008 R2. I can manually run
the script and everything works, but if I try to schedule the script everything works except for the Excel PowerShell commands. I've have tried:
Created the Desktop folders for config\systemprofile in System32 and in SysWOW64.
Configured permissions in DCOM for Microsoft Excel Application.
Configured folder permissions for config\systemprofile.
Verified PowerShell is working.
Unchecked the option in the task to only run while logged on.
Does anyone have any idea why this is happening and how I can fix it? Thanks!
Sincerely,
Christopher Beard

You might have to launch the application once as the system account so that it can set up the Excel environment, I've had the same problem when trying to update Excel files from an admin Powershell console using my admin account. Use psexec with
a -s option to run it as system account locally while logged on to the target server:
psexec -s "c:\program files (x86)\microsoft office\office14\excel.exe"
Then you'll most likely be prompted to input initials - which is what I suspect is preventing your code from running properly.
There may be some other more elegant way to handle this, but you'd be better off asking that question in one of the forums devoted to Office products.
I hope this post has helped!

Group Chat feature in Office Communications Server 2007 R2 does not work in Windows Server 2008 R2 domains

   Hello to all, there are two confliting articles about this topic:
   1-
http://technet.microsoft.com/en-us/library/upgrade-domain-controllers-to-windows-server-2008-r2(v=ws.10).aspx#BKMK_Whatsnew : this one says that it does not work "The Group Chat feature in Office Communications Server 2007 R2 does not work in Windows
Server 2008 R2 domains". This article was updated in 2013.
   2-
http://technet.microsoft.com/en-us/library/ee692314(office.13).aspx: this other article says that it will function "Office Communications Server 2007 R2 Group Chat will function in a Windows Server 2008 R2 forest". This article was updated in
2010 and was refered by the first one.
   What is the correct support position for Group Chat feature in Office Communications Server 2007 R2 and Windows Server 2008 R2 domains?
   Regards, EEOC.

Hi,
I notice the following sentence in the link below “Office Communications Server 2007 R2, Group Chat will not function in a Windows Server 2008 R2 forest or when Group Chat member servers are joined to a Windows Server 2008 R2 domain.
We know of an issue with changes in Windows 2008 R2 that requires a Group Chat Client and Group Chat Admin Tools hotfix. The Group Chat Client and Group Chat Admin Tools hotfixes are currently scheduled for mid-April 2010.”
http://blogs.technet.com/b/nexthop/archive/2010/11/06/supportability-for-office-communications-server-2007-r2-and-windows-server-2008-r2.aspx
So in my opinion, if you update to the latest version of Windows Server 2008 R2, OCS Server 2007 R2 and Group Chat Client, Group Chat Admin Tools to the latest version, it should work.
However, the best method for you is make a lab to test the problem firstly.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

In Windows Server 2008 : Powershell can't import-module ActiveDirectory

Hi,
Thank you in advance for any possible help.
I am using Windows Server 2008 with a x64 machine and I have Powershell 3.0.
After searching for similar problems, I found that I have to install the patches KB969166, KB968934, KB967574, KB968930.
This was done and as a result, the "Web Service Active Directory" appeared in "services".
However, the "ActiveDirectory Module for Windows Powershell" is still not visible in "Windows Features" .
What can I do to make it appear ?
Is there a different way to go so I can have "ActiveDirectory" module in the list of modules I can import in Powershell 3.0 ?
Actually, the command "import-module ActiveDirectory" results in a Not Found error.
I would really appreciate your help.
Thank you !
Bill

Hi Bill,
You can't use the Active Directory module on WS2008, it requires WS2008R2 at a minimum.
Don't retire TechNet! -
(Don't give up yet - 13,085+ strong and growing)

Powershell 4.0 on Windows 7 and Windows Server 2008 R2

I have installed .Net Framework 4.5.1, and Powershell 4.0, and having some issues with some cmdlets; primarily dealing with scheduled tasks. Is Get-ScheduledTask available when Powershell 4.0 running on Windows 7 or Windows Server 2008 r2? I
can't seem to find the module to import, and no modules with schedule in their name shows up with running Get-Module -listavailable.
thanks.
DJ

Hi,
No, those cmdlets are only available on WS2012+ or W8+.
Don't retire TechNet! -
(Don't give up yet - 12,575+ strong and growing)

Powershell 2.0 already enabled on my Windows Server 2008 R2 SP1

I have installed the Powershell ISE feature.
Is Powershell 2.0 already enabled on my Windows Server 2008 R2 SP1?
In DISM /Online /Get-Features none of these pre SP1 exist in SP1.
DISM/Online/Enable-Feature/FeatureName:NetFx2-ServerCore
DISM/Online/Enable-Feature/FeatureName:NetFx2-ServerCore-WOW64
DISM/Online/Enable-Feature/FeatureName:MicrosoftWindowsPowerShell
In SP1 features NetFx3 exists but no MicrosoftWindowsPowerShell.
How do I enable PowerShell 2.0?

Hi Philpsophiae,
By default, Windows PowerShell is not installed on a computer that is running Windows Server 2008 R2 Core. You can use the following methods to install Windows PowerShell on a computer that is running Windows Server 2008 R2 Core.
How to install Windows PowerShell on a computer that is running Windows Server 2008 R2 Core
Please feel free to let us know if these methods above are not helpful to you.
Best Regards,
Anna Wang

Sharepoint 2007 and SQL 2008 SP3 on Windows Server 2008 Enterprise SP2 (64-bit)

Is there any documentation we can check if SQL 2008 SP3 is compatible with Sharepoint 2007 SP2 or SP3? Both Sharepoint and SQL servers are running on separate Virtual machines (Windows Server 2008 Enterprise SP2(64-bit)). Currently DB is running on
SQL server 2008 SP2, and we would like to have SP3 loaded on it, but want to find if there is any compatibility issue?
Thanks in advance!
mh

I'm not aware of any known issues with SQL Server 2008 SP3 and SharePoint 2007. I did a quick check and saw one person reporting an issue with their Central Admin site after applying the SQL Server update, but that's it.
With that being said, I would strongly encourage you to test out the application of that SQL Server service pack in a non-production environment well before you apply it in production. There is always a chance that your environment has something set up in
it that would cause an unexpected issue, and the best way to get an idea of whether or not an issue exists is by doing it somewhere else first before you do it in prod.
John
MCITP and MCTS: SharePoint, Virtualization, Project Server 2007
My books on Amazon: The SharePoint 2010 Disaster Recovery Guide and
The SharePoint 2007 Disaster Recovery Guide.
My blog: My Central Admin.

Installing Exchange 2007 on a Windows Server 2008

Hello I am new to the Microsoft forum and I have a quick question and please let me know if im posting my question in the wrong place. Im doing a school project were you have two servers with Windows Server 2008 installed on them. The first server suppose
to have Active directory and domain services followed by dns which I did. The second server which I just found out suppose to have installed Netframework 3.0, Wpa and Desktop experience roles then install Microsoft Exchange 2007. Well my issue is when I try
to install exchange on my second server it keeps giving me a error message saying my Active directory cannot be contacted or may not exist and that my second server has the wrong security credentials. I've taken the steps that Microsoft has advise by checking
my domain. Which I used the command Dcdiag.exe on my first server and it saids the domain is able to be contacted. Also when I joined my second domain I made sure to put the domain name of the first server in all caps followed by /Administrator and my password
and it said welcome to the domain. So has anybody run into that type of error message when trying to install exchange 2007 on a separate server? Lastly forget to include I also have web server IIS installed on the second server as well. Exchange is then asking
for IIS 7.0 ? So any tips or troubleshooting would be helpful since my professor wasn't much a help and I gotta turn this lab stuff in by next week.
thanks gmoney38

Not sure I need to check that through the dns is working far as ive seen in the server manager . Because I remember before I did this one command for the dns and it said something was wrong with the host A record. So I went through the hierarchy of
windows to that file and opened it up through the notepad it showed my loopback ip address 127.0.0.1 and localhost and not my domain name which I choose contoso01.com so from a previous forum I read if you change the localhost name to that domain name
that it would help but im not sure if this would in my case. Thanks for answering my question Mr. Ed but I still need some more help through!
gmoney38 ps plus im using vmware for this project to have the two servers i wonder if this is why im having issues!

Windows Server 2008 R2: Using PowerShell to send a MSI file to all workstations

Hello!
We are currently using Windows Server 2008 R2. In the upcoming months, we are releasing new software. Instead of touching all the machines with gpupdate /force, we would like to know if we could somehow use Windows PowerShell and send that
command to all the computers in our organization? We are currently in the process of using Group Policy Management to set up the new GPO. After we create them, we would like to send the MSI file to all workstations. I know it is SUPER easy to do within Windows
Server 2012... as I have read articles and seen screenshots. I am just having a hard time figuring out how to make it work with Windows Server 2008 R2.
Thanks!
Megan

New-PSSession -computername Computer
where Computer is one of your remote computers. If that succeeds, great! But I'm guessing it won't and enabling that on all of your computers would require more effort than what you're trying to accomplish in the first place.
Psexec is free to download and you don't have to deploy it:
http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
As far as identifying your target computers, it really depends on your environment. Get-ADComputer is effective, but the example I provided above would get literally every computer in your active directory - is this something you want to deploy to
any and all servers, workstations, etc? How big and complex is your AD? Is this something you need to coordinate with all your systems around about the same time, or can it be staggered? Do you expect your target computers not to reboot between
now and then? I know that's a lot of questions, but your question is loaded and not easy to answer without knowing more about your environment.
What about this?
http://technet.microsoft.com/en-us/library/jj134201.aspx
There is a requirement to have certain firewall exceptions on your target systems, but hopefully they are because that is the best approach.
I hope this post has helped!

Create a child or subdomain in a field or domain in Windows Server 2008 R2 SP1 using Powershell

I am trying to create a child or subdomain in a field or domain in Windows Server 2008 R2 SP1 using Powershell.
ps>powershell.exe -noprofile -command "&{ start-process powershell -ArgumentList '-noprofile -file C:\Users\Administrator\Documents\Powershell\psfile.ps1' -verb RunAs}"
psfile.ps1
([WMIClass]"\\sandpit\root\MicrosoftDNS:MicrosoftDNS_Zone").CreateZone("subdomain.domain.com", 0, $False)

This is a duplicate of a duplicate of a duplicate.
I think this is the current:
http://social.technet.microsoft.com/Forums/scriptcenter/en-US/734be028-438d-433c-b3f7-676c0490b61d/create-a-child-or-subdomain-in-a-field-or-domain-in-windows-server-2008-r2-sp1-using-powershell?forum=winserverpowershell
Don't retire TechNet! -
(Don't give up yet - 12,830+ strong and growing)

Is is possible to install X64 windows server 2008 R2 on Virtual machine 2007 Service pack1?

I am trying to install window server 2008R2 X64 on virtual machine 2007 service pack 1. But unable to proceed. while refering various forum,
It is listed that from service pack1 we can install windows 7 & window server 2008 std edition. But nowhere it listed that window server 2008R2 is supported or not.
Can one let me know if it fisible to install window server 2008R2 X64 on virtual pc 2007 or any work around.
Thanks,
AK

I'd ask them over here.
https://social.technet.microsoft.com/Forums/en-us/home?forum=virtualserver
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Windows Server 2008 R2: Script create multi users with Windows Powershell

Dear All,
I have windows server 2008 R2 Active Directory Domain Service. I want to create multi users by using Windows PowerShell.
Could you guide?
BR,
Khemarin Set
[email protected]

Dear Awinish,
Your link very my solution. but i'm very basic with Powershell and I never have experience with it.
This is the link original script that you are provide:
function Select-FileDialog
param([string]$Title,[string]$Directory,[string]$Filter="CSV Files (*.csv)|*.csv")
[System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms") | Out-Null
$objForm = New-Object System.Windows.Forms.OpenFileDialog
$objForm.InitialDirectory = $Directory
$objForm.Filter = $Filter
$objForm.Title = $Title
$objForm.ShowHelp = $true
$Show = $objForm.ShowDialog()
If ($Show -eq "OK")
Return $objForm.FileName
Else
Exit
$FileName = Select-FileDialog -Title "Import an CSV file" -Directory "C:"
$ExchangeUsersOU = "OU=ExchangeUsers" # I don understand, I have all users are store in all-users ou
$domain = [System.DirectoryServices.ActiveDirectory.Forest]::GetCurrentForest()
$DomainDN = (([System.DirectoryServices.ActiveDirectory.Forest]::GetCurrentForest()).Domains | ? {$_.Name -eq $domain}).GetDirectoryEntry().distinguishedName
$final = "LDAP://$DomainDN"
$DomainPath = [ADSI]"$final"
$cOU = $DomainPath.Create("OrganizationalUnit",$ExchangeUsersOU)
$cOU.SetInfo()
$UserInformation = Import-Csv $FileName
$OUPath = "LDAP://$ExchangeUsersOU,$DomainDN" # I don understand
$UserPath = [ADSI]"$OUPath"
Write-Host "---------------------------------------------------------------"
Write-Host "Creating LAB Users"
Write-Host ""
Write-Host "---------------------------------------------------------------"
Foreach ($User in $UserInformation){
$CN = $User.samAccountName
$SN = $User.Surname
$Given = $User.givenName
$samAccountName = $User.samAccountName
$Display = $User.DisplayName
$LABUser = $UserPath.Create("User","CN=$CN")
Write-Host "Creating User: $User.samAccountName"
$LABUser.Put("samAccountName",$samAccountName)
$LABUser.Put("sn",$SN)
$LABUser.Put("givenName",$Given)
$LABUser.Put("displayName",$Display)
$LABUser.Put("mail","$samAccountName@$domain")
$LABUser.Put("description", "Lab User - created via Script")
$LABUser.Put("userPrincipalName","$samAccountName@$domain")
$LABUser.SetInfo()
$Pwrd = $User.Password
$LABUser.psbase.invoke("setPassword",$Pwrd)
$LABUser.psbase.invokeSet("AccountDisabled",$False)
$LABUser.psbase.CommitChanges()
Write-Host "Script Completed"
If posible, could you help to correct script as: I have domain name: hello.net. All user are store in all-users ou.
BR,
Khemarin Set
[email protected]

Opening Excel Workbook Fails when run from Scheduled Task on Windows Server 2008 Rw

Hi,
I have a little vbs script that instantiates the Excel.Application object and then opens a work book to perform some tasks on it. The script runs fine when run from the command line. When I attempt to run it as a scheduled task (it is supposed to update
data that is pulled from a SQL Server at regular intervals), it fails with the following error:
Microsoft Office Excel cannot access the file 'c:\test\SampleWorkbook.xlsm'. There are several possible reasons: .....
The file does exist. The path reported in the error is correct. The account under which the task is running is the same account I use to run it from the command line. User Account Control is not enabled, and the task is set up to run with highest privileges.
When I run the same script through the Task Scheduler from a Windows Server 2003 machine, it works without issue.
I was just wondering if somebody on this forum has run into a similar issue in connection with Windows Server 2008 R2 and figured out what the magic trick is to make it work. I'm sure it is rights related, but I haven't quite figured out what which rights
are missing.
Thanks in advance for any advice you may have.

This is truly killing me ... trying to get it working on Windows Server 2012 without success.
I desperately need to automate running Excel macros in a "headless" environment, that is non-interactive, non-GUI, etc.
I can get it to work using Excel.Application COM, either via VBScript or Powershell, successfully on many other Windows systems in our environment - Windows Server 2008 R2, Windows 7 (32-bit), etc., -BUT-
The two servers we built out for running our automation process are Windows Server 2012 (SE) - and it just refuses to run on the 2012 servers - it gives the messages below from VBScript and PowerShell, respectively-
I have tried uninstalling and re-installing several different versions of Microsoft Excel (2007 Standard, 2010 Standard, 2010 Professional Plus, 32-bit vs. 64-bit, etc.), but it makes no difference.
Would be extremely grateful if any one out there has had any success in running Excel automation on Server 2012 in a non-interactive environment that they could share.
( I have tried adding the "%windir%\syswow64\config\systemprofile\desktop"
folder, which did fix the issue for me when testing on Windows Server 2008 R2, but sadly did not resolve it on Windows Server 2012 )
[VBScript error msg]
Z:\TestExcelMacro.vbs(35, 1) Microsoft Office Excel: Microsoft Office Excel cannot
access the file 'Z:\TestExcelMacro.xlsm'. There are several possible reasons:
• The file name or path does not exist.
• The file is being used by another program.
• The workbook you are trying to save has the same name as a currently open work
[Powershell error msg]
Exception calling "Add" with "0" argument(s): "Microsoft Office Excel cannot open or save any more documents because th
ere is not enough available memory or disk space.
To make more memory available, close workbooks or programs you no longer need.
To free disk space, delete files you no longer need from the disk you are saving to."
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : ComMethodTargetInvocation
You cannot call a method on a null-valued expression.
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : InvokeMethodOnNull

Powershell Windows Server 2008 R2 - SP 2007

Similar Messages

Maybe you are looking for