I'm attempting to install the Azure Recovery Services Agent on a 2016 Standard Server Core machine. It installs fine, but when I try to browse to the vault credential file, I get an exception that appears to be related to visual themes not existing since it's server core:
I've also tried setting up Azure Powershell to do backups through there, but when I try to login I get an error related to IEFrame.dll:
Login-AzureRmAccount : The type initializer for 'Microsoft.IdentityModel.Clients.ActiveDirectory.Internal.WindowsFormsWebAuthenticationDialogBase' threw an exception.: Unable to load DLL 'IEFRAME.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
When I run Login-AzureRmAccount on a Desktop Experience server, it pops up a window to login, which apparently uses IE. I've also tried Import-AzurePublishSettingsFile, which works, but it still needs me to run Login-AzureRmAccount after running that.
Does anyone know of a command-line way to set the vault credentials for the Recovery Services agent? Or how to login in Powershell without IE?
Download the latest PowerShell release (minimum version required is: 1.0.0) and then Verify you have Windows PowerShell version 3.0 or 4.0. To find the version of Windows PowerShell, type this command at a Windows PowerShell command prompt.
$PSVersionTable
Verify that the value of PSVersion is 3.0 or 4.0. If not, see Windows Management Framework 3.0 or Windows Management Framework 4.0.
And then you can install Microsoft Azure Recovery Services Agent through PowerShell command lets on windows server 2016.
Related
I have downloaded the IIS Powershell snapin IISPowershellSnapin.26IISPowershellSnapin.exe
Unfortunately installing on a windows 2012 Remote desktop doesn't succeed.
The error is:
Microsoft Webinstaller couldn't find the product you tried to install.
Either the link you clicked is incorrect or you may be overwriting
your feed with different feed.
I have downloaded it from the site:
http://www.iis.net/downloads/microsoft/powershell
The manual gives the following Prerequisites:
The IIS PowerShell Snap-in requires the following prerequisites:
•Windows Server 2008, Windows Server 2008 R2, Windows Vista Service
Pack 1, or Windows 7 •Microsoft PowerShell 1.0 or 2.0
So nothing is said about Windows Server 2012.
Is there another executable for Windows Server 2012 or is there another problem.
http://www.iis.net/learn/manage/powershell/installing-the-iis-powershell-snap-in
I have allready checked whether the IIS Management Console is installed and it is installed.
Maybe this executable needs internet connection to install?
On our RDP we have no internet connection so this could be the cause as well.
Simply don't. PSSnapIns are obsolete; everything runs on modules now. The IIS Snap-In has been superseded by the WebAdministration module, which provides a superset of functionality.
Install the module on a >2008R2 server with the following PS:
Add-WindowsFeature Web-Scripting-Tools
This will not cause a service interruption. If it needs a reboot, it will tell you so. You might need to restart your PowerShell console, although this is unnecessary in my experience. After installation, run the cmdlet:
Import-Module WebAdministration
I wonder if anyone has encountered the above issue:
I was able to install the server successfully but when it comes to run the utility that configures the octopus settings, I get the following error
One or more windows features need to be enabled before continuing.
and then I get this afterwards:
"DISM.exe /Online /Enable-Feature /FeatureName:IIS-ASPNET
/FeatureName:IIS-NetFxExtensibility /ALL"
In order to enable the missing feature.
This has now been done successfully. But everytime i try to run Octopus deploy administrative tool I keeping getting the same error.
Is there something I'm missing regarding components I need to have on to the 2012 windows server.
I have never encountered the errors you are mentioning. That said, have you performed a full GUI install of Octopus Deploy, or just the server core? To make it work properly on Windows Server 2012 you need to do a full GUI install.
This must be quite an old version of Octopus - only the 1.x versions required IIS to install the Octopus server (and I don't think it supported Server Core).
The 2.x and 3.x versions don't use IIS (we are a self-hosted NancyFX service).
I'm getting an error when I try to start an Application Pool in IIS7.
The error is called Service WAS was not found on computer'.'.'
I then googled "download Windows Process Activation Service (WAS) and I can't seem to find away to download it.
I'm running this on AWS on a remote desktop from my Windows 7 OS.
It is included in Windows and no additional download is needed.
You need to open Turn Windows features on or off in Control Panel and install it from there.
I'm running VS 2010 under Windows 8. After installing NuGet, and running Package manager console I get the following message:
Error: The Package Manager Console requires PowerShell 2.0 runtime, which is not detected on this machine. Please install the PowerShell 2.0 from http://support.microsoft.com/kb/968929 and restart Visual Studio.
I know that PowerShell 3.0 is installed automatically along with Windows 8. Why would this error message pop up?
While the Windows Powershell 2.0 Engine feature is on by default in Windows 8, you need to turn on .Net 3.5 to actually use it, as mentioned here:
On Windows 8, the Windows PowerShell 2.0 Engine feature is turned on
by default. However, to use it, you need to turn on the option for
Microsoft .NET Framework 3.5, which it requires.
Follow the steps in the above link to get it working.
While PowerShell 3.0 on Windows 8 is installed by default, PowerShell 2.0 isn't. You can go into Programs and Features and select "Turn Windows Features On or Off" and from there you can select Windows PowerShell 2.0 for installation.
We have few windows services developed using .Net framework 1.1(VS2003).For each windows service an msi installer(set up project) is created to make installation easier.These installers are able to install windows services successfully in windows XP.But these installers unable to install windows service in WIN7 though I have admin privileges on the machine in which I am trying install them.While I am trying to install the windows service in win7, Through msi installer,installation is progressing till 90%.After that it is neither completing nor throwing an error.I am unable to understand what the problem is.
I tried following ways.
1.Opened cmd window in admin mode and tried to execute the msi with the command msiexec -i --Din't work
2.Right clicked on the actual exe(windows service exe) file and tried to run it in admin mode.--Din't work
3.Changed the UAC to never notify, restarted the machine and then tried to install--Din't work
4.Right clicked on both exe and msi and open their properties and changed the compatibility to lower version of windows and tried to install--Din't work
One thing I have noticed is that for all the custom actions of our windows service installer, primary output of our main project(exe) was given as input.I build the msi installer by removing all the custom actions.Then i tried to install it in win7.Then it was installed.But during the installation system not prompted for account details (which is the actual case while installing windows service) and also the service was not appeared in services manager window.
I spent somuch time to identify the cause and resolution.But I dint find any posts on this issue.I suspect that the problem is with custom actions.But not sure.If the problem is with custom actions please let me know how to overcome it.
Please provide a resolution for this issue or share me if there are any links which talks about this.
FWIW, .NET 1.1 isn't supported on Win7. Also I'm guessing you are using InstallUtil custom actions to drive the setup of your .NET Windows Service. These are very fragile and you can eliminate all those brittle points by refactoring and using the ServiceInstall ServiceControl tables in MSI.