I would like to know can we install and configure the windows self hosted agent on Azure Classic Machines? I have already created in ARM machines. I don't have classic machines from my end for testing but having at my client environment. We can't create Classic machines as well now (As it has been deprecated). Before requesting my client, I just want to get some clarity this is possible in the classic machines or not ?
Before requesting my client, I just want to get some clarity this is
possible in the classic machines or not ?
Classic mode is just one deployment model, just as Lex Li commented, the types of virtual machines doesn't matter in your scenario. Only the operating system makes sense for installation of self-hosted agents.
Check prerequisites of self-hosted agent:
Windows 7, 8.1, or 10 (if using a client OS)
Windows 2008 R2 SP1 or higher (if using a server OS)
PowerShell 3.0 or higher
.NET Framework 4.6.2 or higher
Only tips above have effect on the installation and usage of windows self agents. Hope it helps to resolve your puzzle.
Related
We are currently using multiple self-hosted build agents with Windows 10 as the operating system. In various pipelines in Azure Devops (whether Online or OnPremis), we have not had any bad experiences or questioned the OS we chose over the many years.
Now IT approached me and asked if there was anything wrong with using Windows Server 2019/2022 as the OS for a self-hosted build agent. I guess in the long run it would be a price advantage.
But are there any other advantages or disadvantages between Windows Server 2019/2022 and Windows 10/11?
There are no other advantages or disadvantages between Windows Server 2019/2022 and Windows 10/11. Only cost... and maybe system requirements of your build/external components.
Microsoft's own documentation provides the links to the images used for various operating systems, on top of which Microsoft-hosted agents get created.
For Windows Server 2019, the link shows bash as one of the tools included, and it also mentions WSL1 (Windows Subsystem for Linux v1) as installed. And it works just as expected, with Bash tasks running just fine inside Azure DevOps pipelines.
We're currently in the process of setting up our own self-hosted Windows agents, and we're looking for this capability as well. But to my knowledge, having Linux tools such as bash working on Windows requires 1) WSL installed and 2) a Linux distribution installed per a specific user. The procedure for deploying on Windows Server is here.
WSL doesn't currently have multiple-user support (GitHub issue here) and trying to run Linux tools as LOCAL SYSTEM presents challenges of their own. So in this context, how does the image used by the Microsoft-hosted Azure DevOps agents allow them to seamlessly run bash?
I heard about Cygwin, and know that it can provide similar functionality, but for now I'm trying to get bash configured similar to how it's done on Microsoft's own hosted agents.
As of this time, however, I think it is not supported running bash in Azure DevOps self-hosted Windows agent.
The Bash task runs on the agent as the user "NT Authority \ Network Service". However, we cannot install Linux distribution for this user. It will show that the user haven't logged in.
But for Microsoft, its virtual machines should have a specific user from whom bash starts rather than the default NT Authority \ Network Service.
My Clearcase Version: 7.1.0 .
My os is windows 7, after I installed Clearcase. I couldn't create a dynamic view by using Create View.And I found that when i start clearcase service from control panel, there is only two service.
Is there any ways to correct this problem except to download a higher version.
ClearCase 7.1.2 is deployed on our Windows 7 at work.
However, when I see that there is only two services, that means MVFS (which is a device, not a driver) has failed to install properly.
The usual fix is to uninstall and reinstall ClearCase.
But there is no guarantee for 7.1.0.
The OP adds:
I have reinstall it three times, but the problem still exists
That confirms 7.1.0 is not supported (at least for the dynamic views part) on Windows 7.
As "System Requirements for ClearCase 7.1.x" confirms, Windows7 SP1 actually needs 7.1.2.3 at minimum.
And even then, you can have some issue: " PM54437: Windows 7 64bit MVFS clients flood albd_server of the View Server host with ALBD_FIND_SERVER RPCs" (which needs 7.1.2.6)
So getting the latest 7.1.x is recommended.
In your case though, since it isn't possible to get a version above 7.1.0, you can try and install a Virtual PC Windows Xp on your Windows 7.
Microsoft Virtual PC for Windows (formerly Connectix Virtual PC) is a client based software virtualization application that allows simultaneous operating systems to run on a single PC.
Each virtual machine emulates a complete hardware system—from processor to network card—in a self-contained, isolated software environment, enabling the simultaneous operation of otherwise incompatible systems.
ClearCase does support Virtual PC.
Can both clients be installed and used at the same time ?
The purpose of using both is based needs to develop for Lync 2010 while still using Communicator 2007 in a corporate environment. Or would a developer be forced to have two different machines/VMs/boot environments ?
No - you can't run both side-by-side. Installing Lync will uninstall Communicator.
However, you can use a registry hack (unsupported, unfortunately) to enable your copy of Lync to run against your OCS infrastructure. This works for R2, not 100% sure about R1.
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator]"DisableServerCheck"=dword:00000001
If you're serious about Lync development, the best solution is to build a server environment specifically for developing against.
Trying to develop and test an ASP.NET MVC 2 as well as a hosted WCF app where the client is limited to IIS 6.0 (OS Windows 2003). I am developing and testing in Windows 7 which has IIS 7. I do not have access to a Windows 2003 disk, so creating a VM doesn't appear to be a viable option for me...
Any suggestions or tips would be greatly appreciated
Update:
Lucas' response led me to consider a virtual dedicated server... Going to try that for a testing environment.
You don't have many options
You bend (get a MSDN subscription or Win 2k3)
Your client bends (upgrades to Win7/2k8)
Find someone you know who can let you use an IIS 6 machine.
Get your client to let you use one of their machines during development
You can virtual PC it. If you can use Windows XP, M$ provides a virtual machine + WinXP trial. It's more for using IE6 I think, but I don't think it limits application installation like IIS.
I don't have the link anymore, but it's provided by M$ from their download area