Windows server 2012 Install-WindowsFeature command executing extreamly slow

New server installed and we wanna install server features on it using powershell.
Script start working, but nothing changed during long period time. Installation progress 24%.
Internet is not accessable. Features installing from iso image mounted to vm.
It's the same image which used for server installation.
Any ideas- what's wrong?
Command is:
Install-WindowsFeature -Name
$Feature-Source
$windowsDistribLocal-LogPath
$LogPathLocal
resulted command is:
Install-WindowsFeature -Name NET-Framework-Core -Source D:\ -LogPath C:\temp\installlog.txt
In a log file was:
2408: 2013-12-25 15:02:48.404 [ServerManagerPS]           Complete initializing log file.
2408: 2013-12-25 15:02:48.606 [ServerManagerPS]           23326f59-1a36-403b-a2bb-1346f85867a5 Enumerate server component ended with Success.
2408: 2013-12-25 15:02:49.935 [ServerManagerPS]           23326f59-1a36-403b-a2bb-1346f85867a5 Alter server component started. Component names: NET-Framework-Core,NET-Framework-Features
2408: 2013-12-25 15:02:49.950 [ServerManagerPS]           23326f59-1a36-403b-a2bb-1346f85867a5 Alter server component ended with InProgress. The progress is 20
2408: 2013-12-25 15:02:50.965 [ServerManagerPS]           23326f59-1a36-403b-a2bb-1346f85867a5 Alter server component started. Component names: NET-Framework-Core,NET-Framework-Features
2408: 2013-12-25 15:02:50.981 [ServerManagerPS]           23326f59-1a36-403b-a2bb-1346f85867a5 Get alteration state ended with InProgress. The progress is 24.
2408: 2013-12-25 15:02:51.997 [ServerManagerPS]           23326f59-1a36-403b-a2bb-1346f85867a5 Alter server component started. Component names: NET-Framework-Core,NET-Framework-Features
2408: 2013-12-25 15:02:51.997 [ServerManagerPS]           23326f59-1a36-403b-a2bb-1346f85867a5 Get alteration state ended with InProgress. The progress is 24.
2408: 2013-12
2408: 2013-12-25 15:07:36.510 [ServerManagerPS]           23326f59-1a36-403b-a2bb-1346f85867a5 Alter server component started. Component names: NET-Framework-Core,NET-Framework-Features
2408: 2013-12-25 15:07:36.510 [ServerManagerPS]           23326f59-1a36-403b-a2bb-1346f85867a5 Get alteration state ended with InProgress. The progress is 24.
WinServ2012 on virtual box.

Hi,
Based on your description, I do the same operation in my Lab environment (Hyper-v and Windows Server 2012). Unfortunately, this issue can’t be reappeared. So, before
going further, would you please let me confirm something?
Did you mean that there was no error message when this issue occurred, just the progress was stuck at 24%? How long did you wait for the change approximately? Finally,
can the feature be installed successfully or not?
Meanwhile, please locate to C:\ Windows\ Logs\ CBS folder and check the
CBS log if you can find some clues.
If anything I misunderstand or more details you can provided, please don’t hesitate to let me know.
Hope this helps.
Best regards,
Justin Gu

Similar Messages

CRM 2015 installation hangs without errors on Windows Server 2012 installed in a VM

I have installed a Windows Server 2012 and SQL Server 2012 on a VM using VMware Player and then installed Dynamics CRM 2013, working out all the configuration problems.
The installation hanged once without errors and when I tried it again it was installed, no problems. Dynamics CRM 2013 works without issue.
Then I copied the machine, uninstalled the Dynamics CRM 2013 and started installing CRM 2015. However this time without errors the installation hangs even though I tried more than 5 times.
There are no errors, installation program is not unresponsive and task manager shows nothing out of the ordinary.
I have also tried this on multiple physical and virtual PCs to no avail.

Try to Delete the registry files of CRM before you start the installation : HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSCRM

New Windows Server 2012 install won't boot after installing Hyper-V role.

I have just installed Windows Server 2012 onto a Dell PowerEdge R310. Everything worked okay until I installed the Hyper-V role. After that, when it tries to boot, I get "Your PC ran into a problem and needs to restart. We're just collecting
some error info, and then we'll restart for you. (0% complete)" for a split second, then the system reboots into Automatic Repair mode.
In Automatic Repair mode, my options are Refresh your system (which tells me the drive that Windows is on is locked), Reset your system (which tells me there is no partition), and Automatically Fix your PC (which tells me it can't fix it).
I have updated to the latest version of the BIOS (1.11.0, which Dell states adds Windows Server 2012 support).
I'm at a loss.. I've tried everything I can think of. Has anyone run into this issue and figured out a solution? The only references I can find to this issue talk about Gigabyte motherboards with USB 3.0, but this server pre-dates USB 3.0 by
quite a bit.

Hi,
Not only the BIOS but the iDRAC and storage part also need to ne up date check, have a look at the following list to see what you need for Server 2012:
http://en.community.dell.com/techcenter/os-applications/w/wiki/3868.dell-bios-support-for-windows-server-2012.aspx
If any info was collected during the error then have a look in the event viewer or look for a kernel/memory dump file so you can try to find the issue, in many cases a driver, anti-virus sofware or 3rd part service can cause these kind of issues.
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer
MCSE:Server Infrastructure, MCSE:Desktop Infrastructure, MCSA Server 2012, Citrix CCIA & CCEE, Cisco CCNA, VMware VCP 3/4/5 Blog: http://www.citrix-guru.com and http://www.rds-support.eu Twitter: @dnyvandam

Windows server 2012 R2 PXE boot is unworkable slow, I have this exact same set-up working in 2008 R2 What can I do?

Hi there
I'm trying to deploy a windows 7 image through Windows deployment services via PXE boot from a 2012 R2 server.
Issue: PXE boot is extremely slow, it takes up to more than 60 minutes for the device to download download the PXE boot
Things I already tried to get this up and running:
I've tried to change the TFTP block size via command prompt and via regedit
I've changed the settings on the tab of the WDS role (go to WDS role -> properties on server -> Tab "tftp")
Both actions resulted in PXE boot being even slower than it already was.
To make sure this is not because of our environment I’ve set up the same configuration on a windows server 2008 R2, here PXE boot image is downloaded to the machine within 3 minutes.
Both servers are set up through Hyper-V this is the configuration:
2008 R2:
Memory: 4096 MB
1 Virtual processor
IDE controller 2 hard drives
Network adapter
2012 R2:
Memory: 4096 MB
32 virtual processors
SCSI controller 2 hard drives
Network adapter
I can’t imagine that PXE boot is not working because of the differences of the Hard drives controllers or because of the amount of the virtual processors.
Windows server 2012 R2 seems to handle PXE boot TFTP differently in comparison to 2008 R2.
Do you guys know what I can do/try to get this working?

Hi Jacques Rodrigues,
You can run Windows Deployment Services on Hyper-V virtual machines,
that the performance will often be degraded, particularly during the Trivial File Transfer Protocol (TFTP) download phase. This phase is very resource-intensive and may
fail if insufficient resources are available on your server running Hyper-V.
If you are using multicast, Check if IGMP Snooping is enabled i.e. Routers that support multicasting. In particular, Internet Group Membership Protocol (IGMP) snooping should
be enabled on all devices. This will cause your network hardware to forward multicast packets only to those devices that are requesting data. If IGMP snooping is turned off, multicast packets are treated as broadcast packets, and will be sent to every device
in the subnet.
The related KB:
Windows Deployment Services Overview
http://technet.microsoft.com/en-us/library/hh831764.aspx
I’m glad to be of help to you!
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.

Windows Server 2012: Installing Windows Identity Foundation runtime

Hello!
I'm trying to install Windows Identity foundation runtime (Windows6.1-KB974405-x64.msu) on a Server 2012 Standard and keep getting this error:
This package installs properly on my Windows 7 prof workstation.
Thank you in advance,
Michael

Hello,
Any reason not to use the following?
(Powershell)
Add-WindowsFeaturewindows-identity-foundation
Regards
MCITP: Enterprise Messaging Administrator 2010 MCTS: Lync Server 2010, Configuring MCSE

Can I install Windows server 2012 r2 in HP Workstation xw4600

I want to install win srv 2012 r2 in my workstation only for practice , can i install it in hp xw4600

Hi,
I agree with Tim that it depends on your computer configuration. Besides, please refer to the requirements for installing Windows server 2012:
Installing Windows Server 2012
In addition, the drivers in the link below would be helpful to you:
Hp Workstation Xw4600 Windows Server 2012 64-bit Drivers
Note: Microsoft is providing this information as a convenience to
you. The sites are not controlled by Microsoft. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Best regards,
Susie

New Mac Pro (late 2013), Boot Camp, Windows Server 2012

Does new Mac Pro (late 2013) support Windows Server 2012 install by Boot Camp?

No.
Boot Camp: System requirements for Microsoft Windows operating systems - Apple Support
Apologies, Templeton Peck, did not see your post.

Unable to add File Server Resource Manager Tools on Windows Server 2012 - Errors on restart and roll back install

Unable to install Windows Server 2012 Feature - [Tools] File Server Resource Manager Tools.
Installs, however when I restart the server error messages appears saying feature unable to install, windows reverting changes.
In the Setup event logs have the following information message "Update FSRM-Infrastructure of package FSRM-All failed to be turned on. Status: 0x800f0922"
Does anyone have any idea's on why this Feature can not be installed ??
Scott

Hi Shaun
Tried both of your suggestions, however neither strategy worked.
Strategy 1
Tried installing via powershell - "install-windowsfeature -name fs-resource-manager -includemanagementtools"
Feature un-installed itself during the restart.
Attempted to use the command "DISM /online /remove-feature /featurename:FSRM-Infrastructure-Services". However
this did work because one the Service was'nt installed or two because there was no command option for "/remove-feature"
PACKAGE SERVICING COMMANDS:
/Add-Package - Adds packages to the image.
/Remove-Package - Removes packages from the image.
/Enable-Feature - Enables a specific feature in the image.
/Disable-Feature - Disables a specific feature in the image.
/Get-Packages - Displays information about all packages in the image.
/Get-PackageInfo - Displays information about a specific package.
/Get-Features - Displays information about all features in a package.
/Get-FeatureInfo - Displays information about a specific feature.
/Cleanup-Image - Performs cleanup and recovery operations on the image.
Strategy 2
Tried installing via powershell, using the following command DISM
/online /enable-feature /featurename:FSRM-Infrastructure-Services, however got the same result, the install backed out during the restart.
All up back to where I started?

Unable to install windows features on windows server 2012 core datacenter

If I attempt to install, remove, or get windows features via powershell in windows server 2012 core datacenter I get the following error:
PS C:\Users\BB> Invoke-Command -ComputerName CORE1 {Install-WindowsFeature Web-CertProvider}
The given key was not present in the dictionary.
+ CategoryInfo : NotSpecified: (:) [Install-WindowsFeature], KeyN
otFoundException
+ FullyQualifiedErrorId : System.Collections.Generic.KeyNotFoundException,
Microsoft.Windows.ServerManager.Commands.AddWindowsFeatureCommand
+ PSComputerName : CORE1
I get the same error regardless of weather I use install-windowsfeature, remove-windowsfeature or get-windowsfeature. I've tried it on the server, and remotely.
I've also tried managing the computer remotely using another windows 2012 server using the server manager GUI. That causes the server manager to crash with the following error:
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: servermanager.exe
Problem Signature 02: 6.2.9200.16384
Problem Signature 03: 50107b22
Problem Signature 04: mscorlib
Problem Signature 05: 4.0.30319.17929
Problem Signature 06: 4ffa57ca
Problem Signature 07: 210b
Problem Signature 08: c
Problem Signature 09: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB
OS Version: 6.2.9200.2.0.0.400.8
Locale ID: 1033
Additional Information 1: 7a77
Additional Information 2: 7a77983701ecc7870d72712ffa4c3c88
Additional Information 3: 0b4b
Additional Information 4: 0b4b0ba1592ebbc56adc05832bb92aa6
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=190175
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
The server is running all Microsoft updates. Rebooting doesn't help. I've checked the event logs and I don't see anything relevant.
Help!
Thanks
Brad

Hi,
I would like to suggest you first run get-windowsfeature command on the core locally not remotely. And if it works, then try to remote run it.
Invoke-Command -ComputerName CORE1 {get-WindowsFeature }
Regards,
Yan Li
Cataleya Li
TechNet Community Support

[Forum FAQ] How to install and configure Windows Server Essentials Experience role on Windows Server 2012 R2 Standard via PowerShell locally and remotely

As we all know,
the Windows Server Essentials Experience role is available in Windows Server 2012 R2 Standard and Windows Server 2012 R2 Datacenter. We can add the Windows Server
Essentials Experience role in Server Manager or via Windows PowerShell.
In this article, we introduce the steps to install and configure Windows
Server Essentials Experience role on Windows Server 2012 R2 Standard via PowerShell locally and remotely. For better analyze, we divide this article into two parts.
Before installing the Windows Server Essentials Experience Role, please use
Get-WindowsFeature
PowerShell cmdlet to ensure the Windows Server Essentials Experience (ServerEssentialsRole) is available. (Figure 1)
Figure 1.
Part 1: Install Windows Server Essentials Experience role locally
Add Windows Server Essentials Experience role
Run Windows PowerShell as administrator, then type
Add-WindowsFeature ServerEssentialsRole cmdlet to install Windows Server Essentials Experience role. (Figure 2)
Figure 2.
Note: It is necessary to configure Windows Server Essentials Experience (Post-deployment Configuration). Otherwise, you will encounter following issue when opening Dashboard.
(Figure 3)
Figure 3.
2. Configure Windows Server Essentials Experience role
(1) In an existing domain environment
Firstly, please join the Windows Server 2012 R2 Standard computer to the existing domain through the path:
Control Panel\System\Change Settings\”Change…”\Member of. (Figure 4)
Figure 4.
After that, please install Windows Server Essentials Experience role as original description. After installation completed, please use the following command to configure Windows
Server Essentials:
Start-WssConfigurationService –Credential <Your Credential>
Note: The type of
Your Credential should be as: Domain-Name\Domain-User-Account.
You must be a member of the Enterprise Admin group and Domain Admin group in Active Directory when using the command above to configure Windows Server Essentials. (Figure 5)
Figure 5.
Next, you can type the password for the domain account. (Figure 6)
Figure 6.
After setting the credential, please type “Y” to continue to configure Windows Server Essentials. (Figure 7)
Figure 7.
By the way, you can use
Get-WssConfigurationStatus
PowerShell cmdlet to
get the status of the configuration of Windows Server Essentials. Specify the
ShowProgress parameter to view a progress indicator. (Figure 8)
Figure 8.
(2) In a non-domain environment
Open PowerShell (Run as Administrator) on the Windows Server 2012 R2 Standard and type following PowerShell cmdlets: (Figure 9)
Start-WssConfigurationService -CompanyName "xxx" -DNSName "xxx" -NetBiosName "xxx" -ComputerName "xxx” –NewAdminCredential $cred
Figure 9.
After you type the commands above and click Enter, you can create a new administrator credential. (Figure 10)
After creating the new administrator credential, please type “Y” to continue to configure Windows Server Essentials. (Figure 11)
After a reboot, all the configurations will be completed and you can open the Windows Server Essentials Dashboard without any errors. (Figure 12)
Figure 12.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Part 2: Install and configure Windows Server Essentials Experience role remotely
In an existing domain environment
In an existing domain environment, please use following command to provide credential and then add Server Essentials Role: (Figure 13)
Add-WindowsFeature -Name ServerEssentialsRole
-ComputerName xxx -Credential DomainName\DomainAccount
Figure 13.
After you enter the credential, it will start install Windows Server Essentials role on your computer. (Figure 14)
Figure 14.
After the installation completes, it will return the result as below:
Figure 15.
Next, please use the
Enter-PSSession
cmdlet and provide the correct credential to start an interactive session with a remote computer. You can use the commands below:
Enter-PSSession –ComputerName
xxx –Credential DomainName\DomainAccount (Figure 16)
Figure 16.
Then, please configure Server Essentials Role via
Add-WssConfigurationService cmdlet and it also needs to provide correct credential. (Figure 17)
Figure 17.
After your credential is accepted, it will update and prepare your server. (Figure 18)
Figure 18.
After that, please type “Y” to continue to configure Windows Server Essentials. (Figure 19)
Figure 19.
2. In a non-domain environment
In my test environment, I set up two computers running Windows Server 2012 R2 Standard and use Server1 as a target computer. The IP addresses for the two computers are as
below:
Sevrer1: 192.168.1.54
Server2: 192.168.1.53
Run
Enable-PSRemoting –Force on Server1. (Figure 20)
Figure 20.
Since there is no existing domain, it is necessary to add the target computer (Server1) to a TrustedHosts list (maintained by WinRM) on Server 2. We can use following command
to
add the TrustedHosts entry:
Set-Item WSMan:\localhost\Client\TrustedHosts IP-Address
(Figure 21)
Figure 21.
Next, we can use
Enter-PSSession
cmdlet and provide the correct credential to start an interactive session with the remote computer. (Figure 22)
Figure 22.
After that, you can install Windows Server Essentials Experience Role remotely via Add-WindowsFeature ServerEssentialsRole cmdlet. (Figure 23)
Figure 23.
From figure 24, we can see that the installation is completed.
Figure 24.
Then you can use
Start-WssConfigurationService cmdlet to configure Essentials Role and follow the steps in the first part (configure Windows Server Essentials Experience in a non-domain environment) as the steps would be the same.
The figure below shows the status of Windows Server Essentials.
Figure
25.
Finally, we have successfully configured Windows Server Essentials on Server1. (Figure 26)
Figure 26.
More information:
[Forum
FAQ] Introduce Windows Powershell Remoting
Windows Server Essentials Setup Cmdlets
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

SharePoint Foundation 2013 installed on Windows Server 2012 not sending out email notification

I have a server where i installed SP Foundation 2013 on top of Windows Server 2012. I have configured the SMTP as well as the outgoing SMTP in Central Administration
of SharePoint. When i create an alert on a document library, its did not sent any email notification on the changes made to the document in the document library. So, i created a workflow to send out email using SPD2013. The workflow run, but it cannot sent
out email with error saying that outgoing email is not configured correctly. I have checked with another server which i installed SP foundation 2013 on top of Windows Server 2008 R2 - its sending out email just fine using same configuration and outgoing SMTP.
I need help to resolve this issue or at least the cause of the problem.
Any help is greatly appreciated.

Try below:
http://social.technet.microsoft.com/wiki/contents/articles/13771.troubleshooting-steps-for-sharepoint-alert-email-does-not-go-out.aspx
Go to Central Admin ---->Operations----->outgoing email settings and verify that SMTP server is mentioned correctly
2) Test the connectivity with the SMTP server.
In order to do that follow these steps:
Open cmd
telnet <SMTP server name> 25 ( We connect smtp server to the port 25)
you should see a response like this 220 <servername> Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at date and time
Beware that different servers will come up with different settings but you will get something
If you dont get anything then there could be 2 possible reasons, either port 25 is blocked or
the smtp server is not responding.
For testing response from your server
For testing response say ehlo to it.
Type :
ehlo <servername>
output:
250 <servername> Hello [IP Address]
Now a test mail can be sent from that SharePoint server.
Now we need to enter the From address of the mail.
Type :
mail from: [email protected]
output:
250 2.1.0 [email protected]….Sender OK
It's time to enter the recepient email address.
Type : rcpt to: [email protected]
output:
250 2.1.5 [email protected]
Now we are left with the data of the email. i.e. subject and body.
Type : data
output:
354 Start mail input; end with <CRLF>.<CRLF>
Type:
subject: this is a test mail
Hi
This is test mail body
I am testing SMTP server.
Hit Enter, then . and then Enter.
output:
250 2.6.0 <<servername>C8wSA00000006@<servername>> Queued mail for delivery
Type: quit
output:
221 2.0.0 <servername> Service closing transmission channe
3) Check alerts are enabled for your web application
verify if the windows timer service is running or not.
Run this stsadm command to check that
Stsadm.exe -o getproperty -url http://SharePoint-web-App-URL -pn alerts-enabled
This should return <Property Exist="Yes" Value="yes" />
If you don’t get this, Enable alerts by:
stsadm.exe -o setproperty -pn alerts-enabled -pv "true" -url http://SharePoint-web-App-URL
If its already enabled, try turn off and turn on it back.
4) Check the Timer job and Properties
Go to
MOSS 2007: Central Administration > Operations > Timer Job Definitions (under Global Configuration)
In SharePoint 2010: Central Administration > Monitoring > Review Job Definitions
Check whether the "Immediate Alerts" job is enabled for your web application. check these properties:
job-immediate-alerts
job-daily-alerts
job-weekly-alerts
stsadm.exe -o getproperty -url "http://Your-SharePoint-web-App-URL" -pn job-immediate-alerts
The expected output is:
<Property Exist="Yes" Value="every 5 minutes between 0 and 59"/>.
If you don’t get this, run the following command to set its value.
stsadm.exe -o setproperty -pn job-immediate-alerts -pv “every 5 minutes between 0 and 59" -url http://Your-SharePoint-web-App-URL
5) Check whether the account is subscribed for alerts and it has a valid email account. This should be the first thing to check if the problem persists for some users not for all.
6) Then check if at all those users have at least read permission for the list. Because the first mail should go out for every user without security validation but the next ones won't be delivered unless the user has at least read
permission.
7) If it is happening for one user, can also try to delete and re add the user in the site.
8) Most importantly , you should try this one.
Run this SQL query to the content db < Select * from Timerlock>
This will give you the name of the server which is locking the content database and since when.
In order to get rid of that lock
Go to that server which is locking the content db and then restart the windows timer service.
within some time it should release the lock from content db, if not then at the most stop the timer job for some time
Once the lock will be released then try to send some alerts
You will surely get the email alert.
I found this is the most probable reason for alert not working most of the time. We should start troubleshooting with above steps before coming to this step for any alert email issue but from step 1 to step 7 are best for new environments or new servers.
If the issue is like this ,alert was working before and suddenly stopped working without any environmental change then above conditions in step 1-7 should be ideally fine.
Even after this if it is not working, then you can try these few more steps too
9) Try re-registering the alert template:
stsadm -o updatealerttemplates -url http://Your-SharePoint-Web-App-URL -f "c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\XML\alerttemplates.xml" -LCID 1033
10) Try to clear the configuration cache
If this helped you resolve your issue, please mark it Answered

Error while installing Microsoft Identity Extensions Setup during installation of SharePoint Foundation 2013 on Windows Server 2012

Hi All,
When i try to manually (no internet connection on the server) install SharePoint 2013 Prerequisites on Windows Server 2012 I get the below error
I have installed .Net Framework 3.5, 4.0 and Windows Identity Foundation using Add server roles or features from the server manager.
From Software & Hardware requirements for SharePoint 2013 give
Prerequisites for SharePoint 2013 I can see that the identity extensions are available only of Windows Server 2008 R2 and not for windows server 2012. Can you please provide the link for windows server 2012?
I have installed all the prerequisites required except Microsoft Identity Extensions.
Raghavendra Shanbhag | Blog: http://moss-solutions.blogspot.com
Please click "Propose As Answer " if a post solves your problem or "Vote As Helpful" if a post has been useful to you.
Disclaimer: This posting is provided "AS IS" with no warranties.

I fixed it by installing Microsoft Identity extensions from command line, please find command line below.
C:\Windows\System32>msiexec.exe /i "C:\SharePoint2013ServerFiles\prerequisiteinstallerfiles\MicrosoftIdentityExtensions-64.msi" /quiet /norestart
Note: In the above command C:\SharePoint2013ServerFiles\prerequisiteinsTallerfiles is the path where I had downloaded all the prerequisites for SP2013
This will install Microsoft Identity Extensions and creates registry entries, which will help the SharePoint 2013 Prerequisite installer to complete the setup
For more details check out
here
Raghavendra Shanbhag | Blog: http://moss-solutions.blogspot.com
Please click "Propose As Answer " if a post solves your problem or "Vote As Helpful" if a post has been useful to you.
Disclaimer: This posting is provided "AS IS" with no warranties.

Install sharepoint 2013 on Windows server 2012, Microsoft Identity Extensions issue !!!!!!!!!

Sharepoint 2013 comes with prerequisitesinstaller.exe to install the software required for the actual Sharepoint installation.
I 've installed Windows server 2012 in the R2 edition as well as Standard edition, but installing the prerequisites ends with an issue for the Microsoft Identity Extensions (MIE) on both versions (screenshot).
The 2012 R2 server has been updated with all latest files by executing Windows update.
In case of the Server 2012 R2, MIE is already installed , but somehow the Sharepoint installation is missing something.
I al;so tried removing default install to let prerequisiteinstaller.exe to install it's own version, but that did not help.
When I skip the prerequisites remaining items, the Sharepoint installation stops directly , requesting the missing items.
I've tried several Sharepoint server installation files, including the 180 days free version.
Screenshots will be uploaded after my account has been checked......

Hi Jay,
Installing SharePoint Server 2013 on a computer that is running Windows Server 2012 R2 could lead to unexpected behavior, therefore, Microsoft does not support SharePoint Server 2013 in Windows Server 2012 R2.
SharePoint Server 2013 with Service Pack 1 and SharePoint Foundation 2013 with Service Pack 1 will offer support for Windows Server 2012 R2.
Refer to:
SharePoint 2013 Support for Windows Server 2012 R2
In addition, as Dave suggested, for the sharepoint server issue, please post in the dedicated forum for a better response.
Best Regards,
Anna Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Error during configuration process while installing obiee 11.1.1.7.0 in windows server 2012

HI..
I'm having an issue while installing obiee 11g(11.1.1.7.0) in windows server 2012 and using the database as ms sql server 2008. During configuration process after the installation process is completed , here the process is stopped at "Step:executing opmnctl start configuration_obisch1" status "failed"
Here is the error:
Error
    opmnctl task failed
    Step Executing: opmnctl start coreapplication_obisch1 failed
    Configuration Action "Executing opmnctl start coreapplication_obisch1 " has failed. please check log files...
any help would be great
thanks..

Friend,
Installer file size is:
Size: *1.23 GB (1,323,085,837 bytes).*
Size on disk: *1.23 GB (1,323,089,920 bytes).*
I tested also disabling antivirus on my PC and disconnect the power cord before starting the installation of JDeveloper. In both tests the result was the same.
Some additional recommendations to solve this case.
Thank you for supporting.
Edited by: Luis_vkacito on Nov 15, 2012 6:48 AM

Install Windows Server 2012 R2 VM on Storage Spaces with Storage Tiers

Hey guys
In my small/medium sized company we will soon update to Windows Server 2012 R2. I would like to implement virtual servers using Hyper-V. I didn't find a lot of information about Hyper-V in combination with storages spaces and autoamted storage tiers.
And this is very confusing to me as it seems to me that this would be the best practice as it is the most cost-efficient and most elegant solution.
My ideal scenario:
With Hyper-V I virtualize two Windows Server 2012 R2 instances. So two separate virtual machines.
I use the following disk setup:
1x cheap HDD 40GB for hyper-v server 2012 r2 core.
2x SSD 200GB (enterprise-grade)
2x HDD 4TB (7.2k, enterprise-grade)
Step 1:
I will install Hyper-V Server 2012 R2 Core on the 40GB HDD. Via command line, I will create a storage pool with automated tiered storage using the SSDs and the HDDs in mirrored mode the following way:
With Tiered Storage, I create a storage pool containing the SSDs and the HDDs. Then I create storage space A (1TB) and B (3.2TB) with the SSDs in a mirrored setup and the HDDs in a mirrored setup. The SSDs for the „hot files“ and the HDDs for the „cold files“.
Step2:
Ontop of the storage space A I want to install the first Windows Server 2012 R2 instance with Active directory. On storage space B I want to install the second Windows Server 2012 R2 instance for a business application to run on it.
Conclusion:
The SSDs are mirrored and therefore one SSD can fail.
The 4TB HDDs are mirrored and therefore one HDD can fail.
I have a fast and easy scalable environment.
But in the Internet I found many information that it’s not possible to install an operating system onto a storage tier.
Question 1:
Is this setup possible?
Question 2:
If this setup is possible, why is not everyone doing it?
Question 3:
Is it possible to do Step 1 over a GUI from a remote machine?
Question 4:
If the creation of Storage Tiers in the Hyper-V Server 2012 R2 is not possible. Would it work to use a Windows Server 2012 R2 as a parent system on the 40GB HDD? To do Step 1?
I would gladly get some feedback of people knowing Storage Tiers well.
Thanks a lot!

I would absolutely prefer a GUI. But a Windows Server 2012 R2 Standard Licence allows you to run two VM machines.
It also grants you a physical installation ("POSE" in the licensing documents). You can buy one copy of WS2012R2 Standard, install it on the hardware, enable Hyper-V, and then operate two virtual machines with WS2012R2 Standard ("VOSE"
in the licensing documents). The only restriction is that the management operating system (POSE) can only run services and applications meant to manage the virtual machines and/or the management operating system. The Hyper-V Server license is the same way
so it's not really any different.
In short, given the benefits of the GUI at your stage of learning, you have no solid reason not to install the full system and take advantage of it. You can disable the GUI later once you get your footing. Or not. Whatever suits you. However, in response
to your Question 3, you can do this all remotely. Once you get WS2012R2 installed in a guest, you can use it to manage the management operating system if you want. There are many options.
But then I would also need to have redundancy on the 40GB HDD as if this HDD brakes, all others brake as well?
Yes, you're going to want some redundancy for the management operating system. But, you've listed 5 drives in your original layout. You don't really have a 5-bay system, do you? Is there an empty sixth bay? Could you not get two 40 GB drives instead of one
and use hardware RAID-1?
Eric Siron
Altaro Hyper-V Blog
I am an independent blog contributor, not an Altaro employee. I am solely responsible for the content of my posts.

Windows server 2012 Install-WindowsFeature command executing extreamly slow

Similar Messages

Maybe you are looking for