Upgrading PowerShell 2.0 to 3.0 on a Windows Server 2008 SP 2 Enterprise Certification Authority server

Hello All:
Are there any caveats to upgrading PowerShell 2.0 to 3.0 on a customer's Certification Authority server? The customer will also be upgrading to SCCM 2012 and employ this server as a Distribution Point.
Any feedback would be greatly appreciated.
Thank you.

Hi Erik,
I haven't tried to upgrade powershell on Certification Authority server, however, Windows Management Framework 3.0 requires Microsoft .NET Framework 4.0, and you need to change .NET version on server 2008 SP2.
For more detailed installation instruction, please follow this article:
Windows Management Framework 3.0
If there is anything else regarding this issue, please feel free to post back.
Best Regards,
Anna Wang

Similar Messages

Upgrade DTSX packages from VS 2010 with SQL Server 2008 to VS 2013 and SQL Server 2014

Hello everyone,
I’m very new to SSIS world. I’ve been assigned a task to upgrade the existing packages running in VS 2010 with SQL Server 2008 to VS 2013 and SQL Server 2014. And then submit the migration report to my client.
On very quick search at Google, I've found the following link. It seems like I just need to open the existing SSIS project in VS 2013 and follow the wizard.
https://msdn.microsoft.com/en-us/library/cc280547.aspx
Can anybody please advise, are there any other things need to be taken care while doing this up gradation process?
Please share your experience.
Any help would be much appreciated.
Thanks, <b>Ankit Shah</b> <hr> Inkey Solutions, India. <hr> Microsoft Certified Business Management Solutions Professionals <hr> http://ankit.inkeysolutions.com

Hello Arthur,
Thank you for the response.
I just got an access of the packages. They are of VS 2008 and not 2010.
Do you know how to upgrade VS 2008 packaged to VS 2013?
When I tried to open the solution file in VS 2013, it says "incompatible".
Any help would be much appreciated.
Thanks,
Ankit
Thanks, <b>Ankit Shah</b> <hr> Inkey Solutions, India. <hr> Microsoft Certified Business Management Solutions Professionals <hr> http://ankit.inkeysolutions.com

Upgrading windows server 2003 domain controller to windows server 2008

Hello friedns :
We have a company with about 2000 users , and two windows server 2003 domain controllers , one of them acts as a primary domain controller , and the other acts as secondary domain controller , all the FSMO s are on the primary DC ,we have decided to upgrade all of our servers from windows server 2003 to windows server 2008 , the first step is to upgrade the domain controllers to windows server 2008 , our domain controllers are so sensitive and has to be active 24 hours a day , i have stress upgrading it to windows server 2008 , what is the best solution to upgrade it with no risk ?
( i have an opinion but i am not sure and i dont have any guide about it , i want to install a windows server 2008 and promote it as an additional domain controller to the windows server 2003 DC and the transfer all the FSMOs to it , and then promote the first domain controller !!! is that possible ? if yes , is there any guide about it? )
If there is a guide available for it please let me know . (Specially if there is a tip & trick)
thank you guys.
Network is my LOVE

Hi,
This TechNet online article might be helpful for you.
How to Upgrade Domain Controllers to Windows Server 2008 or Windows Server 2008 R2
http://technet.microsoft.com/en-us/library/ee522994(WS.10).aspx
For your convenience, I have list some general steps for your reference.
Since the following operation have potential damage to Active Directory database, it is highly suggested that you'd better perform a full backup of Active Directory (System State) firstly. Also it is better to test the following procedure in a similar lab environment first.
General Steps:
=============
1. Verify the new server's TCP/IP configuration has been pointed to the current DNS server.
2. Make the new server become a member server of the current Windows Server 2003 domain first.
3. Upgrade the Windows Server 2003 forest schema to Windows Server 2008 schema with the "adprep /forestprep" command on old server.
Please run the "adprep.exe /forestprep" command from the Windows Server 2008 installation disk on the schema master. To do this, insert the Windows Server 2008 installation disk, and then type the following command:
Drive:\sources\ADPREP\adprep.exe /forestprep
4. Upgrade the Windows 2003 domain schema with the "adprep /domainprep" command on old server.
Please run the "adprep.exe /domainprep" command from the Windows Server 2008 installation disk on the infrastructure master. To do this, insert the Windows Server 2008 installation disk, and then type the following command:
Drive:\sources\ADPREP \adprep.exe /domainprep
5. Insert Windows Server 2008 Installation Disc in the new server.
6. Run "dcpromo" on new server to promote it as an additional domain controller in existing Windows 2003 domain, afterwards you may verify the installation of Active Directory.
Please refer to:
How to Verify an Active Directory Installation in Windows Server 2003
http://support.microsoft.com/kb/816106
7. Verify the new server's TCP/IP configuration has been pointed to current DNS server.
8. Enable Global Catalog on new server and manually Check Replication Topology and afterwards manually trigger replication (Replicate Now) to synchronize Active Directory database between 2 replicas.
Please note: It will some time to replicate GC between DC, please wait some time with patience.
9. Disable Global Catalog on the old DC.
10. Transfer all the FSMO roles from the old DC to the new DC.
Please refer to:
How to view and transfer FSMO roles in Windows Server 2003
http://support.microsoft.com/kb/324801
11. Verify that the old DNS Server Zone type is Active Directory-Integrated. If not, please refer to:
How To: Convert DNS Primary Server to Active Directory Integrated
http://support.microsoft.com/kb/816101
Note: Active Directory Integrated-Zone is available only if DNS server is a domain controller.
12. Install DNS component on new server and configure it as a new DNS Server (Active Directory Integrated-Zone is preferred). All the DNS configuration should be replicated to the new DNS server with Active Directory Replication.
13. Make all the clients change TCP/IP configuration to point to new server as DNS.
14. You may configure TCP/IP on all the clients, or adjust DHCP scope settings to make them use the new DNS server.
Please note: It is a good practice to make the old DC offline for several days and check whether everything works normally with the new server online. If so, you may let the old DC online and run DCPROMO to demote it.
Hope it helps.
Regards,
Wilson Jia
This posting is provided "AS IS" with no warranties, and confers no rights.

Upgrade for Windows Server 2008 R2 to Windows Server 2012 R2

Hi Guys,
I am having an issue with upgrading one of our Servers. When I try to upgrade the Server it starts the process perfectly fine without any issues, it reboots and displays the Windows Server 2012 R2 Logo and then I get a black screen and it hangs. I waited
around 5 hours today before rebooting the Server and letting it rollback the changes that setup had made.
Original Server Setup
OS: Windows Server 2008 R2
Other Applications: MS SQL Server 2012 with SP2
Removed Applications: Symantec Backup Agen
Hardware: Virtual Server ESXi 5.0
I have upgraded other servers without any issues but they haven't had SQL Server installed on them, so I am guessing that this is the issue but SQL Server 2012 sp2 is Supported by Windows Server 2012 R2. Does anyone have any suggestions?
Kind Regards,
Thomas

Hi All,
Yes we are running ESXi 5 U 2 I am looking at how much of a pain this will be to build a new VM for this database server, as it contains our Citrix database which we have had issues with in the past. I might end up just leaving this server for the moment
and move onto another server and hopefully not have any more issues.
Thank you all for your suggestions to resolving this issue.
Kind Regards,

[Forum FAQ]How to upgrade Windows Server 2008 R2 with a GUI to Windows Server 2012 Server Core

We found that some customers willing to upgrade Windows Server 2008 R2 GUI to Windows Server 2012 Server Core recently. This article provides detailed steps to perform the upgrade.
Analysis
Upgrading from Windows Server 2008 R2 with a GUI installation to Windows Server 2012 with Server Core directly
is not supported. If you do that, you will receive the error message below(Figure 1) in Compatibility report:
Figure 1.
In these scenario, you can upgrade to Windows Server 2012 firstly. After the upgrade process is completed, you can switch freely between Server Core and Server with a GUI modes.
Produces
You can follow the steps below to perform an upgrade from Windows Server 2008 R2 with a GUI installation to Windows Server 2012 Server Core mode:
1. Upgrade to Windows Server 2012 with a GUI mode
1) Firstly, please boot into Windows Server 2008 R2 with a Windows Server 2012 installation DVD inserted.
2) Select the operating system you want to install with a GUI mode.
We can see 2 options (Server Core Installation or Server with a GUI) for each operating system version. (Figure 2)
Figure 2.
Note: Please make sure you have enough disk space on system partition. Or you will get such an error in Compatibility report.(Figure 3)
Figure 3.
After the Compatibility check, the installation will continue. It will take several minutes until upgrading is done.(Figure 4)
Figure 4.
2. Switch the GUI mode to Server Core
Method 1: Using Server Manager
1) Open Server Manager, click
Manger and select “Remove Roles and Features” to start the
Remove Roles and Features Wizard.
2) In Features,
uncheck the box next to the “User Interfaces and Infrastructure” option, and then click “Next”. (Figure 5)
Figure 5.
Now tick the “Restart the destination Server automatically if required” box, then click “Remove”. (Figure 6)
Figure 6.
Method 2: Using Windows PowerShell
There are multiple ways to remove the GUI via Windows PowerShell, we introduce the way of using the ServerManager module.
You can also run the commands in Windows PowerShell with an administrator to remove the GUI feature:
“Import-Module ServerManager”
“Uninstall-Windowsfeature Server-Gui-Shell –Restart”
or
“Uninstall-WindowsFeature Server-Gui-Shell, Server-Gui-Mgmt-Infra –Restart”
It will take a period of time to remove the GUI feature and reboot. When the system boots up, you will get into the Windows Server 2012 with Server Core mode. (Figure 7)
Figure 7.
More information:
Switch between Full and Server Core in Windows Server 2012 using PowerShell 3.0
http://blogs.technet.com/b/puneetvig/archive/2012/10/16/switch-between-full-and-core-in-windows-server-2012-using-powershell-3-0.aspx
Windows Server Installation and Upgrade
http://technet.microsoft.com/en-us/windowsserver/dn527667.aspx
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hi,
Brian is right, for mange the Server 2008r2 sp1 we recommend use the Windows 7 or 7.1 platform.
More information:
Remote Server Administration Tools for Windows 7 with Service Pack 1 (SP1)
http://www.microsoft.com/en-us/download/details.aspx?id=7887
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Upgrade Virtual machine running server 2008 r2 to server 2012 r2.......

Hi Everyone.........
I have virtual Server machine Current Running Server 2008 r2 data-center, and try to upgrade server 2012 r2 data-center but unfortunately not Upgrade and Showing Errors like below....
how to upgrade virtual server machine in server 2012 r2, Please help me for this Issue .

I recommend doing a fresh install of Server 2012 R2 on the bare metal, enable the Hyper-V role and migrate the VMs over using these steps:
Shutdown the VMs on the current 2008 or 2008 R2 Hyper-V host(s)
In Hyper-V Manager, delete all snapshots and saved states of all VMs.
Set all the VM vNICs to use static MAC
Export each VM
On the new 2012 R2 Hyper-V server, import the VMs
Sam Boutros, Senior Consultant, Software Logic, KOP, PA http://superwidgets.wordpress.com (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable) _________________________________________________________________________________
Powershell: Learn it before it's an emergency http://technet.microsoft.com/en-us/scriptcenter/powershell.aspx http://technet.microsoft.com/en-us/scriptcenter/dd793612.aspx

AppFabric crashes IIS Manager when Powershell 4 is installed (Server 2008 R2 SP1)

When Powershell 4 is installed on a Server 2008 R2 SP1 box with AppFabric 1.1, IIS Manager will fail.
If you go to IIS Manager and plus open the node for your server (to look at your sites or app pools) you get an error like the following:
Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: inetmgr.exe
Problem Signature 02: 7.5.7600.16385
Problem Signature 03: 4a5bd0a5
Problem Signature 04: System.Management.Automation
Problem Signature 05: 1.0.0.0
Problem Signature 06: 4ce7c787
Problem Signature 07: 106d
Problem Signature 08: a6
Problem Signature 09: PUYL1YSRBZLI4302TJNBZ1HF4QQMYKVP
OS Version: 6.1.7601.2.1.0.272.7
Locale ID: 1033
If you look at the application event log, you will also see:
IISMANAGER_CRASH
IIS Manager terminated unexpectedly.
Exception:System.Management.Automation.CmdletInvocationException: The method or operation is not implemented. ---> System.NotImplementedException: The method or operation is not implemented.
   at Microsoft.ApplicationServer.Management.Tools.PowershellHost.NoConsolePSRawUserInterface.get_BufferSize()
   at System.Management.Automation.Internal.Host.InternalHostRawUserInterface.get_BufferSize()
   at Microsoft.PowerShell.Commands.Internal.Format.ConsoleLineOutput.get_ColumnNumber()
   at Microsoft.PowerShell.Commands.Internal.Format.OutCommandInner.ProcessOutOfBandPayload(FormatEntryData fed)
   at Microsoft.PowerShell.Commands.Internal.Format.OutCommandInner.ProcessPayload(FormatEntryData fed, OutputContext c)
   at Microsoft.PowerShell.Commands.Internal.Format.OutCommandInner.ProcessObject(PSObject so)
   at Microsoft.PowerShell.Commands.Internal.Format.OutCommandInner.ProcessRecord()
   at Microsoft.PowerShell.Commands.Internal.Format.FrontEndCommandBase.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Internal.PipelineProcessor.DoStepItems(Object input, Hashtable errorResults, Boolean enumerate)
   at Microsoft.PowerShell.Commands.Internal.Format.CommandWrapper.Process(Object o)
   at Microsoft.PowerShell.Commands.Internal.Format.SubPipelineManager.Process(PSObject so)
   at Microsoft.PowerShell.Commands.Internal.Format.OutputManagerInner.ProcessRecord()
   at Microsoft.PowerShell.Commands.Internal.Format.FrontEndCommandBase.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
If you then uninstall AppFabric 1.1, everything starts working again. I need Powershell 4 with AppFabric 1.1. Any ideas?
I wonder if the below breaking change in Powershell 4 is causing the issue:
In Windows PowerShell 4.0, if a module uses the DefaultCommandPrefix key in its manifest, or if the user imports a module with the Prefix parameter, the ExportedCommands property of the module shows the commands in the module with the prefix. When you run
the commands by using the module-qualified syntax ModuleName\CommandName, the command names must include the prefix.

We didn't have this issue with Powershell 4.0, but with Server 2008 R2 SP1 and AppFabric 1.1. The solution for us was to install the
Upgrade Readiness Tool. No problems with Inetmgr and Clr20R3 after the hotfix was applied.

Unable to upgrade SQL Server 2008 R2 to SQL Server 2012 SP1

I'm encountering error after error, after successfully installing the upgrade advisor (which took some doing) and running it with essentially no warnings/errors (the one warning was on the connection strings, as I recall -- and all of the warnings had a
"fix after" status.
First failure involved SSRS and the inability to create the "managed account". Backed out the upgrade using http://sqldbanotes.blogspot.com/2013/10/how-to-fix-failed-in-place.html
Now the failure involves SSAS and unable to connect to analysis services with name MSSQLServerOLAPService. That is the logical name for the service, although it shows up as just MSSQLServer when looking at it in the services list. I tried
setting the service account to a local account as well as to Local System -- did not make a difference, the upgrade couldn't apparently find it regardless.
Has anybody successfully done an in place upgrade from SQL Server 2008 R2 to SQL Server 2012?

Hi Bob，
Thanks for your post and I am glad to hear that the issue is resolved. Thanks for you posting a reply to share your solution and I had marked it as answer. That way, other community members could benefit from your sharing.
Regards,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support

Hi! I can't upgrade my iTunes 10.3.1.55 on my Windows XP 2002 SP3 to the latest version of iTunes. Got the message: "A problem has occured with the Windows Installer-package. A program needed for this installation could not be run." What to do?

Hi! I can't upgrade my iTunes 10.3.1.55 on my Windows XP 2002 SP3 to the latest version of iTunes. Got the message: "A problem has occured with the Windows Installer-package. A program needed for this installation could not be run." What to do?

Perhaps let's first try updating your Apple Software Update.
Launch Apple Software Update ("Start > All Programs > Apple Software Update"). Does it launch and offer you a newer version of Apple Software Update? If so, choose to install just that update to Apple Software Update. (Deselect any other software offered at the same time.)
If the ASU update goes through okay, try another iTunes install. Does it go through without the errors this time?

Windows 2008 Standard SP2 inplace upgrade to Windows Server 2008 R2 Standard SP1 failing

Hi All,
I'm encountering an issue with performing an in-place upgrade of Windows Server 2008 SP2 to Windows Server 2008 R2 SP1.
Server details:
Virtual machine running on VMware ESXi 5.
Uninstalled AV and backup software
Domain controller also running AD Certificate Services#
UAC disabled
Running setup as a domain admin
When launching setup, the process completes "Copying Windows Files". After a few seconds or being on "Gathering files, settings and programs 0%", an error appears on screen -
Windows installation encountered an unexpected error. Verify that the installation sources are accessible, and restart the installation.
Error code: 0xC0000005
Errors and information up to the fatal errors in the setupact.log setup summary:
2013-04-28 19:26:35, Info MIG Loading replacement manifest data for Microsoft-Windows-WMI-Core
2013-04-28 19:26:35, Info MIG Loading replacement manifest data for Microsoft-Windows-WSRM-Service
2013-04-28 19:26:35, Info [0x080841] MIG UPGCSIAgent: Enumerating installed manifest source using C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_676975d87cc9b6e6\wcp.dll
2013-04-28 19:26:35, Warning [0x080405] MIG EnablePrivilege: AdjustTokenPrivileges failed (Error:0x514)
2013-04-28 19:26:35, Info CSI 00000001@2013/4/28:18:26:35.866 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7feeff78c85 @0x7fef1646a4e @0x7fef1646676 @0x7fef1647a53 @0x7fef164c291
@0x7feedd728ba)
2013-04-28 19:26:35, FatalError [0x090001] PANTHR Exception (code 0xC0000005: ACCESS_VIOLATION) occurred at 0x000007FEF00498CF in C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_676975d87cc9b6e6\wcp.dll (+00000000001498CF).
Minidump attached (107516 bytes).
2013-04-28 19:26:36, FatalError [0x090001] PANTHR Exception (code 0xC0000005: ACCESS_VIOLATION) occurred at 0x000007FEF00498CF in C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_676975d87cc9b6e6\wcp.dll (+00000000001498CF).
Minidump attached (107788 bytes).
The diagerr.xml has the two minidumps but they are just encoded straight into the xml file. Thanks for any assistance. /Ashley

Hi,
Generally such kind of issues are caused by third party programs such as CD burning programs, device driver etc.
First please refer to this article to see if there is anything helpful:
Guide for Upgrading to Windows Server 2008 R2
http://technet.microsoft.com/en-us/library/ff972408(v=ws.10).aspx
Meanwhile from the description, it mentioned a file under C:\Windows\winsxs. Check the permission of the folder amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_676975d87cc9b6e6 and the file wcp.dll to see if the permission
and ownership are correct compare with the other folders.
Also as it provided 2 minidump files, you will need to use WinDBG to read the minidump files and see if there is any further information.
http://support.microsoft.com/kb/315263
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected]

Windows server 2008 R2 to Windows server 2012 R@ Upgrade

We have Team Foundation server 2010 server configured in our environment.
operating system: windows server 2008 R2 Datacenter
Server installed: Team foundation server 2010 with share point services 3.0.
we need to upgrade this server with windows server 2012 R2 and Team foundation server 2010 as it is.
need to upgrade as below:
operation system windows server 2012 R2 Datacenter
Server Installed : Team foundation server 210 with sharepoint services 3.0 as it is.
I have tried to direct upgrade by running a setup of windows server 2012 R2 but it shows error message if : "
When you upgrade Windows Server 2008 to Windows Server 2012, you receive the following error message:
Windows won’t install unless each of these things is taken care of. Close Windows Setup, take care of each one, and then restart Windows Setup to continue.
Windows needs to be restarted so necessary changes to system files can be made before continuing.
Make these changes:
Turn off these Windows features.
Windows SharePoint Services 3.0 – Please read Microsoft Knowledge Base article: 962216
I have installed sharepoint 3.0 with sp3. but still I am geeing same error.
we need to upgrade operating system,n in place.
Kindly request you for the quick response.

Hi,
To understand more clearly regarding upgrading issue here providing you link for more information.
Upgrade Options for Windows Server 2012 R2
http://technet.microsoft.com/en-us/library/dn303416.aspx
Install and Deploy Windows Server 2012 R2 and Windows Server 2012
http://technet.microsoft.com/en-us/library/hh831620.aspx
Hope it helps!
Regards.

Alternatives to PowerShell automation of Excel (Scheduled Task) in a Windows Server 2012 R2 world

I have a handful of PowerShell scripts that ran as Scheduled Tasks on an old Windows 2008 SP2 server, which output reports as Excel workbooks with multiple worksheets, via a COM object. After migrating these scripts to a new Windows 2012 R2 server,
these scripts no longer function. The Server 2008 system was running Office 2007, and the new Server 2012 R2 server has Office 2013 installed.
What is everyone using on their Server 2012 R2 systems to automate generation of multi-sheet reports in Excel via PowerShell and Scheduled Tasks?
I know that Microsoft has said that automating Office applications server-side in non-interactive mode, but it has worked in the past, until now. (https://support.microsoft.com/kb/257757)
I've tried the OpenXML PowerTools for PowerShell (https://powertools.codeplex.com/), but Export-OpenXMLSpreadsheet will only export a single worksheet, and they don't support adding worksheets to existing files
(am I missing something?). I understand the OpenXML PowerTools can be extended in C#, but I don't C#. The PowerShell cmdlets were released in Jan 2012, but don't look to have been updated since then (updates have been the core C# code).
I've seen recommendations to add C:\Windows\(System32 or SysWOW64)\config\systemprofile\Desktop, but this hasn't worked on Server 2012.
Has anyone been able to get Excel 2013 to cooperate on Server 2012 R2, or come up with a suitable alternative? I'd rather not start running these scripts from my workstation.
EDIT:
I'm not necessarily looking for an Excel answer, since there are OpenXML ways of doing things now without the Excel application.
Here are some of the errors I'm getting when approaching this from different directions. When I use:
$excel = New-Object -comobject Excel.Application$workbook = $excel.Workbooks.Add()
Results in error:
Exception calling "Add" with "0" argument(s): "Microsoft Excel cannot open or
save any more documents because there 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."
At C:\path\to\script.ps1:21 char:2
+ $workbook = $excel.Workbooks.Add()
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : ComMethodTargetInvocation
The server is definitely not lacking for resources.
I can copy a blank XLSX file and use .Open($xlFile) instead of .Add(), but then when I go to open a CSV file to copy/paste the content to a worksheet, I get this one:
Exception calling "Open" with "1" argument(s): "The server threw an exception.
(Exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT))"
At C:\path\to\script.ps1:65 char:2
+ $tempcsv = $excel.Workbooks.Open($CSVFile)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : ComMethodTargetInvocation
Things that I've tried so far, with no success:
I created C:\Windows\System32\config\systemprofile\Desktop and C:\Windows\SysWOW64\config\systemprofile\Desktop as suggested here:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/0751119d-84d5-4a77-8240-1c4802f97375/powershell-scheduled-tasks-wont-start-excel?forum=winserverpowershell
Add Local Launch and Local Activation permissions to the Microsoft Excel Application DCOM Config, Grant "Read & Execute, List folder contents, Read" permissions on the \config\systemprofile\Desktop folder. Grant "Modify, Read & Execute,
List Folder Content, Read, Write" permissions for the account on the following folders:
\config\systemprofile\AppData\Roaming\Microsoft
\config\systemprofile\AppData\Local\Microsoft
as suggested here:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/aede572b-4c1f-4729-bc9d-899fed5fad02/run-powershell-script-as-scheduled-task-that-uses-excel-com-object?forum=winserverpowershell
@ jrv - I will try posting a similar question in the Excel 2013 forum, but since I'm looking for a scripting solution to produce an OpenXML spreadsheet, and not something that necessarily uses the Excel application (though such a solution would not be turned
away), I thought this the more appropriate venue.
(to reiterate from OP) I have seen and acknowledge Microsoft's statements regarding the unsupported nature of automating Office applications in non-interactive environments, but the truth of the matter is, supported or not, it worked in the past (Server
2008), it's what I inherited from my predecessor, and I know I'm not the only one who has been using Excel in this way. I'm only asking fellow scripters, some of whom must also be using Excel in this "unsupported" fashion, how they are automating
creation of their spreadsheet reports after moving to Server 2012. A different system modification to make the Excel comObject continue working as before? Direct manipulation of the OpenXML document? Other solutions that may or may not require launching the
Excel application?

#1 - Ask in Excel 2013 forum.
#2 - Microsoft has repeatedlynoted that this is NOT a supported configuration for Office products.
#3 - What errors are you getting?
#4 - What have you done to debug this:
#5 - No one can be of much help unless you post a very simple example of how this fails.
¯\_(ツ)_/¯

After upgrading ACS 3.3.1 to 4.2 on windows the local database is not working

Hi,
I have upgaded the ACS 3.3.1 for windows server to 4.2. Everything went fine but the local database is not working.
The CD is an upgrade kit from 3.x to 4.2 on windows. I tried to install directly the 4.2 I was able to install but integration with AD/LDAp is not working. Anysay its an upgrade kit so I cant expect it shoud work when install drectly the 4.2 but by upgrading from 3.3 to 4.2 everything should work fine.
I followed the upgradation path as recomended.
Also we have a requirment that once it is upgraded to 4.2 we need to shift the whole thing from the physical server to a virtual machine on VMware ESX server 3.5.
Can anybody pls guide me if anything else to do after the upgradation.
Thanks & Regards
Sachi

Hi Javier,
First of all I was facing a problem of restoring the old database of 3.3 to 4.2. Somehow I overcame that issue by following the below steps. Now local authentication is working fine but AD/other External database authentication is not working. As you told the setting for the unknown users are configured to fetch the credentials from the external database if it is not in the local database.
Do we need to do anything in the AD itself?
Regards
Sachi
Steps for ACS upgrade to 4.2 version
Below are the requested steps mentioned for the up gradation from ACS 3.3.2 to ACS 4.2.
        1)     Take a configuration backup from existing ACS. ACS--->System
configuration----> ACS Backup
2)    now if you have ACS 3.3.2 on server. take backup of the ACS
3)   Insert the cd or if you have the set up on the system then Run the setup of ACS 3.3.4. During the process it will prompt you to
upgrade existing configuration. Make sure you check that option else we will
loose the database. Now you need to hit next.next to finish the 3.3.4 upgrade.
4)     Once you are at 3.3.4, take a backup and keep it handy.
5)     Run the setup of 4.1.1. During this process it will prompt you to
upgrade existing configuration. Make sure you check that option else we will
loose the database. Now you need to hit next.next to finish the 4.1 upgrade.
6)Once you are at 4.1.1.24 take a backup and keep it handy.
7)     Run the setup of 4.2. During this process it will prompt you to
upgrade existing configuration. Make sure you check that option else we will
loose the database. Now you need to hit next.next to finish the 4.2 upgrade.
8)     Once you are at 4.2 take a backup and keep it handy. Now run the
patch 12 and take a backup again.
9)     Now fresh install 4.2 on your new production server and install patch
12. Restore the 4.2 patch 12 backup and you should be all set.

Upgrade from Snow Leopard to Mountain Lion erase my Windows partition?

Dear all,
I know some one might have asked it but I just wanna re-confirm.
Would the upgrade from Snow Leopard to Mountain Lion erase my Windows partition? I am currently using Bootcamp on my Macbook Pro (Late 2010 Version) and I do not have parallel desktop. I asked the same question when Lion was released, but HK Apple Store said YES and Melbourne Apple Store said no. I am a bit confused now.
Thank you for answering. Cheers!

Nothing.
That said, you should ALWAYS have a backup as anything can happen at anytime.

¿Is it possible to upgrade from SCCM 2012 a domain controller in Windows Server 2008 R2 TO 2012 R2?

Hi all.
I want to know if is it possible to upgrade a domain controller from Windows Server 2008 r2 to 2012 r2 installing from SCCM 2012.
Thanks.
Regards.

Hi all.
I want to know if is it possible to upgrade a domain controller from Windows Server 2008 r2 to 2012 r2 installing from SCCM 2012.
Thanks.
Regards.
Anything is possible if you can script it. You could create a task sequence to do the following (with scripts):
1. Demote 2008R2 DC to member server
2. Remove 2008R2 member server from domain
3. Build new 2012R2 member server and join to domain
4. Promote 2012R2 member server to DC
You can do this. However, why would you? Just because you can doesn't mean you should. In my opinion it's more trouble and testing than it's worth. How many times would you need to do this?
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Upgrading PowerShell 2.0 to 3.0 on a Windows Server 2008 SP 2 Enterprise Certification Authority server

Similar Messages

Maybe you are looking for