I was not able to update or install devtoolset on rhel home workstation.
Came across below article which says devtoolset is not available for individual developer (free) subscription.
https://access.redhat.com/solutions/472793
NOTE: As of July 2022, the additional subscriptions listed HERE are entitled to access to RHSCL and DTS.
RHSCL and DTS are not available for use with the following RHEL subscriptions:
Red Hat Enterprise Linux Server, Self-Support
Red Hat Enterprise Linux Workstation, Self-Support
Related
I am going through some Azure training and want to try out the Azure Site Recovery functionality for an Azure Ubuntu 20.04 VM.
The VM is created with the latest standard Ubuntu 20.04 image; replication is enabled but failed:
Error ID: 151113
Error Message:
This version of mobility service doesn't support the operating system
kernel version (5.13.0-1023-azure) running on the source machine.
Please refer the list of operating systems supported by Azure Site
Recovery : https://aka.ms/a2a_supported_linux_os_versions
As this is the most basic configuration I can imagine, I wonder how to set this up correctly so it works.
These are the official instructions I found: https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-quickstart
The VM is a Standard B1ms (1 vcpu, 2 GiB memory). I had started with a smaller one first, but then read that 1GB memory is minimum and upgraded the VM to B1ms.
The kernel version of an out-of-the-box Ubuntu 20.04 installation is 5.13.0-1023-azure; all the supported kernel versions are in the 5.4.* version numbers according to https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-support-matrix#supported-ubuntu-kernel-versions-for-azure-virtual-machines.
The Error you are getting because the updated mobility service version is not compatible with the old version of kernal. You have update to lastet version of kernal.
To support latest Linux kernels within 15 days of release, Azure Site
Recovery rolls out hot fix patch on top of latest mobility agent
version. This fix is rolled out in between two major version releases.
To update to latest version of mobility agent (including hot fix
patch) follow steps mentioned in this article. This patch is
currently rolled out for mobility agents used in Azure to Azure DR
scenario.
Note : Before upgrading operating system/kernel versions, verify if the target version is supported Site Recovery.
Review available updates to find out what you want to upgrade
I'm using an unattended installation of Windows 10 21H2 LTSC using an "answer file" (unattend.xml) on a surface pro 7 plus device.
I have placed SetupComplete.cmd at: %windir%\setup\scripts as suggested from the documentation in the image file (WIM file). I can see the file is in place after Windows installation is done.
Following the installation on the tablet I see that the commands in SetupComplete.cmd were not executed. There is nothing in the log file where SetupComplete.cmd should write to.
Is there something else to do so this file (SetupComplete.cmd) will run? Registry? answer-file?
Any suggestions?
As it seems my issue is related to the following KB:
https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/os-deployment-task-sequence-not-continue
In my case I was using Windows® 10 IoT Enterprise 2021 LTSC
but Setup could not detect that it was an Enterprise edition so did not run the script:
[windeploy.exe] Client OS detected: 1
[windeploy.exe] OEM Licensing detected: 1
[windeploy.exe] **EnterpriseS or Enterprise or EnterpriseSN or EnterpriseN edition detected: 0**
[windeploy.exe] Client OS edition and OEM license detected and no enterprise edition detected, will not run SetupComplete.cmd
This explains why Setup did has decided not to run SetupComplete.cmd - a poor decision since it was an "Enterprise" edition after all.
This seems like a bug in Windows Setup. Still waiting for a resolution from MSFT.
I am trying to setup a Windows 7 Virtual Machine in Azure and I see a list of Windows Server options, but not a plain Windows 7 Professional.
I need Windows 7 for testing purposes.
Do they only support server VMs?
Edit: After Searching I found that Windows 7 Enterprise N is supported. I guess I could use that. But it seems lame that they would not support something so common as Windows 7 Professional...
Windows 7 (and all Windows client OSs) are not supported, or more importantly, licensed for use on ANY cloud service.
Azure gets around this limitation by only allowing Windows Client machines to be run as MSDN development machines. (I imagine being Microsoft helps too)
If you have an MSDN subscription, you will have access to Win7, Win8, and Win10 machines.
So if you wanted to build a business running Windows client machines, licensing would restrict that, but if you're using it as a development machine, that is ok.
So you couldn't, for instance, give everyone in an office access to a Win 10 Machine on Azure.
I am trying to determine if I can configure a development machine for Sharepoint 2013 Enterprise using Visual Studio Pro 2013 and Sharepoint Foundation 2013.
I do not wish to install VS on the production server and run it from there - that is just asking for trouble.
However the budget will not withstand another SP2013 Enterprise license.
I have searched this site and others, but have not found any instance that specifically addresses my question:
can I install SP2013 Foundation (which is free) on my development machine with VS2013 Pro, and use that to build solutions for deployment to my production SP2013 Enterprise server?
The short answer is yes you could do this, but it may not let you do what you need...
So my first addendum to 'yes,' is that the dev machine needs to be running Windows Server 2008 R2 or later and meet all the other hardware and software requirements.
My second is probably a bit more important -- if you develop on SP foundation instead of enterprise you'll be unable to develop and test many of the features that your organization (or your customer, whichever is appropriate) probably purchased the enterprise edition for in the first place.
Something that's also important to note, you wouldn't need to purchase another full enterprise license; you can get an MSDN subscription (platforms or premium for access to SharePoint) that will give you access to software to use specifically for development and testing purposes.
I'm working on a project with CE 6.0 and I need to rebuild the tree. My problem is that I have to update the tree up to May 2009, this requires the 2008 rollup and the following 5 monthly updates, but I can't find them (there's the 2009 rollup and the following 2010 monthly updates).
I can't upgrade to a newer release as our platform is incompatible with R3 and post-May 2009 updates.
Of course if it would be possible to upgrade the platform so that it would be compatible with R3, I would upgrade, but it is currently not possible for two reasons:
There's a third party middleware that's not compatible with R3.
The product that has already been deployed (hundreds of thousands of devices) has currently an image based on CE 6.0 R2 upgraded to May 2009, an I want to recreate that environment.
Is there a place where I can download the "archived" updates?
The Mobile & Embedded Communications Extranet (ECE) is where the embedded channel resources are archived, but it is an authenticated access site. Credentials are usually obtained through the distributor that the embedded product development tools and licenses are obtained from (distributors like Arrow).
The embedded team blog could be a place to begin looking for contact information for folk within Microsoft.
Once you get access, Embedded > Products > Download Center > Windows Embedded > Windows CE contains:
Windows Embedded CE 6.0 R2 Release - Product Download
Applicable to: Embedded Distributors and OEMs Who Purchase Through Distribution
The Microsoft® Update Windows® Embedded CE 6.0 R2 software is now available for download on the ECE. Windows Embedded CE 6.0 R2 provides the latest breakthrough technologies that enable Windows® Embedded CE 6.0 device makers to quickly and easily build small footprint devices that connect to Windows Vista® and Windows® Server 2008.
...
Posted: November 13, 2007
Windows Embedded CE 6.0 Updates contains:
Product Updates for Microsoft® Windows® Embedded CE 6.0.
For individual updates prior to January 2009 please contact your MS Authorized Distributor.