sourcecommand is officially for Unix operating systems family and you can't use it on windows basically. instead, you can use venv\Scripts\activate command to activate your virtual environment.
For windows, type "C:\Users\Sid\venv\FirstProject\Scripts\activate" in the terminal without quotes. Simply give the location of your Scripts folder in your project. So, the command will be location_of_the_Scripts_Folder\activate.
A small reminder, but I had my slashes the wrong way on Win10 cmd. According to python documentation the activate command is: C:\> \Scripts\activate.batWhen you're browsing directories it's e.g. cd .env/Scripts
If you see the 5 folders (Include,Lib,Scripts,tcl,pip-selfcheck) after using the virtualenv yourenvname command, change directory to Scripts folder in the cmd itself and simply use "activate" command.
The script runs without error, but it's not actually completing the intended task (activating the embedded windows 10 pro key). I'm not sure where I'm going wrong. I'm pretty new to powershell so any assistance would be greatly appreciated.
So in effect, to quote, "if Product Key what?". What do you want product key to be? I would say you want the script block below to run if the product key is not null/emtpy, correct? So something like this might work
Thanks for the response. I made the change based on your suggestion and what this did was pull up the GUI version of the windows key activation where it asks to manually enter the key. Progress, you could say, but this script needs to be silent and input that information on it's own. This gives me something to work on, but if you have any more suggestions, I would greatly appreciate it.
I have read the link you propouse, arriving to the fact that the article you propouse doesn't give any solution to activate a digital license from mdt, but some one says that is posible to run the activation troubleshooter, how can I do that, is this posible from mdt or how is the way in an unanttendant deployment scenario, can I run it from powershell?
I have read the link you propouse, arriving to the fact that the article you propouse doesn't give any solution to activate a digital license from mdt, but some one says that is posible to run the activation troubleshooter, how can I do that, is this posible from mdt?, may I run a powershell script to run the activatin troubleshooter
the question is that slmgr.vbs seem to active the license on line, our work station goes through a linux kerberos autentication proxy to access internet to microsoft servers as we don't have KMS, when we try to activate de license we don't arrive to microsfot servers as I explain in:
Can I automatically retrieve the wndows 10 bios license of my work stations already deployed in my domain from VAMT so I can activate them from this software, or on another hand I must get the information of the keys of each computer before, and afteward insert each key into VAMT so I can activate them?.
In other words, I'm interested on having and automatizied process of activating those bios licenses from VAMT as easy as possible, not retrieving the keys and inserting them into VAMT to be activated.
well that's on a local workstation, I suppose vamt behaves the same with remote computers as is based on slmgr, and smlgr can work remotely, even in the proxy scenario picture says that vamt discover the information about licenses, Am I right?.
Hi again Patchfox, we have decided to install mdt and vamt in order to deploy windows 10 profesional in our organization, the question is that we have decided to instal adk in a windows 2012 server r2, as is the only server with direct connection to internet, the questin is, where can I download adk for windows 2012server r2 in oder to manage a domain with windows 10 profesional work stations?, deployment with mdt and activate the licenses in the domain with vamt.
Hi MicaH,
If I have one license server , how to use this powershell script to activate it?
1.I create pc list for csv
2.I run this script for PC list
3.how to add license server kms host for this script?
Windows PowerShell is a utility that lets you automate Windows features including activation of the operating system. You must activate Windows with a valid license before all Windows features are available to the user. PowerShell is an extended form of the Windows command prompt that you can use to customize windows from a window that looks like the DOS prompt.
Query the current license object. You use this object to activate the license, but you must first specify your computer name and query the computer's WMI object. Type the following code to set up the object:
Jim Campbell has been a computer engineer for over five years. He excels in hardware repair, computer programming and troubleshooting, and software design. He is currently attending Florida Atlantic University, pursuing a master's degree in computer and electrical engineering and fine-tuning his technical writing abilities.
Hello Jaideep,
Thanks for the reply. But it didn't work. It's still complaining about the same 'denied permissions' (see attachment)
The fact that most softwares/IDEs tend to have an 'Install for all users' option but oneAPI doesn't is unfortunate.
I have already tried all options on my side, even tried re-installing multiple times. The error is always about the user not having run permissions.
Could you please confirm that you are getting the same error in the command prompt? I assume I got the same error as you got in powershell. I have attached a screen shot for your reference. Please follow the above steps which I mentioned earlier in command prompt (cmd).
Hello Jaideep,
I have followed the steps you have suggested. The error occurs on command prompt as well, as reported in my initial explanation when opening the case.
Only this time the error message was a lot less verbose than on powershell and it is in German, saying "Access denied". I have attached a screenshot.
Hello Jaideep,
Were you able to find a clue why this problem is occuring?
Meanwhile, I am using a non-configured laptop from work to try & see if this problem can be reproduced. And during this attempt at diagnostics, I found another problem with IntelPython during installation, which is reported in this ticket.
I followed the instruction from Intel to diagnose this second new problem. I have replied to the issue here. Once I can install the Base Toolkit first, I can check if the problem with run permissions is still there.
Thank you.
Hari
By default, the Intel oneAPI Base Toolkit is installed in the /opt/intel/oneapi folder, which requires root privileges to manage it. If you would like to bypass using root access to manage your conda environment, then you can clone your desired conda environment using the following command:
To test & find out if the permissions error is because of our company's internal windows configurations/permission settings, I tried installing the Base toolkit on a non-configured laptop, but there it wouldn't even install.
The problem that it won't install seems to be common, with diagnostics in the instruction from Intel in a comment. I have replied to the issue there, uploaded the logs generated during installation with a lot more debug info. But it is on a different computer without any of our company-specific configurations.
If I can install the Base Toolkit on this other laptop first, then I can check if the problem with run permissions is still there.
We suppose if it is installed on "C:\Users\user_name\Intel\oneAPI", is should be run without input administrator passwrd (even for users not in administrator group). I'll verify if this works as we expected.
I tried running it as normal user (not in administrator group) on powershell & cmd (command prompt), & it doesn't run. The usual user account from which development will happen is not going to be in the administrator group.
I have set python, python scripts & libs location into the PATH environment variable, & from powershell it shows on Tab-based auto-complete. So that's working & is not posing a problem.
Intel oneAPI base toolkit can only be installed and run as administrator, if you want to use Intel Distribution for Python without administrator privilege, please try installing via conda which I suggested above!
Does that mean we cannot use intel fortran, C++, MKL library & other tools in the basetoolkit without admin rights? All development in the company happens from a user profile (not in administrator group), without administrator rights.. This problem is only on Windows. In linux it works without any problems but not Linux cannot be used for all applications.
The problem is, even conda won't run without being logged in as administrator. Installing packages should require admin rights & that's understandable but to even run python or conda it not allowed from a user profile.
Hi @Huiyan_C_Intel :
Thanks for the clarification. Infact I don't want the Intel Base Toolkit to be able to run as user but even when it is run as administrator, if it can have an option like "Install for all users", that will also be helpful. But in my case, I can't even run python or conda as user.
In linux, conda works as user & anything installed with conda gets installed under the user home by default & it's cleanly managed there
The other important point is, there are lots of windows IDEs, compilers & development tools that ask for administrator credentials when installing but do allow users to run the application. If just this minor aspect can be corrected in the Intel toolkit, that would be amazing.
I will in the meanwhile try doing the conda installation method.. Thank you.
3a8082e126