- #BAMBOO SOFTWARE WINDOWS 10 HOW TO#
- #BAMBOO SOFTWARE WINDOWS 10 INSTALL#
- #BAMBOO SOFTWARE WINDOWS 10 DRIVER#
- #BAMBOO SOFTWARE WINDOWS 10 WINDOWS 10#
- #BAMBOO SOFTWARE WINDOWS 10 PASSWORD#
#BAMBOO SOFTWARE WINDOWS 10 PASSWORD#
You can also use psexec from Windows Sysinternals to specify a password on the command line. You can overcome the password requirement by running the command manually and using the "/savecred" option once. You need to tell Windows that the command needs higher privileges, and for that you use runas. When you state your Bamboo user can run commands " with administrator privileges" it is not the same as running a command " as an administrator". I understand your system has only "one" account, but Windows has many built-in users that can't be removed. So I'd like to understand how this happens. But they don't fail, so I spent a lot of time trying to figure out what was wrong. If the commands failed, I would know that privileges were wrong. And even while the task is running other parts of the system (like the ODBC framework) can't see these changes. Once the task ends, all those changes are gone. That is the part that really confused me: the `reg add` commands work, the `reg query` commands see the changes, but the changes aren't actually there in the registry.
The main thing I want to know is, why do these registry commands all succeed when I run them from within my Bamboo task, but they don't actually seem to affect the real registry on the system? It would be good to find a way to make this work but that's not actually the main thing I have a question about. If I start a cmd.exe terminal "Run as Administrator", I can do that and the reg command works. Second, no matter what password I enter it says "5: Access is denied." This makes me think I don't know the needed password (I tried the account password for example). There are two problems: first, it asks for a password so it can't be used in a script (however I think I read somewhere there's a way to cache the password so maybe that's possible).
#BAMBOO SOFTWARE WINDOWS 10 HOW TO#
I'm sorry but I'm not a Windows person so I don't know how to figure out these things. I don't know if the bamboo agent process (java) was started with administrator privileges or not. That account is allowed to start programs with administrator privileges. Hi Alvarenga I tried to be clear about the environment but I guess I failed.
#BAMBOO SOFTWARE WINDOWS 10 DRIVER#
And, my ODBC driver (which is trying to look up this driver name) fails saying no such driver exists.īut, when I run these exact same commands via RDP from a cmd.exe with administrator privileges it works fine and the ODBC driver is found. Then in the task script right after the above command I can run: reg query "HKLM\Software\ODBC\ODBCINST.INI\ODBC Drivers"Īnd it prints the driver name I just added.īut then when I RDP to the server and run the same query, it shows nothing. The commands I'm running are things like: reg add "HKLM\Software\ODBC\ODBCINST.INI\ODBC Drivers" /v "Test ODBC Driver" /t REG_SZ /d "Installed" /f Unfortunately I'm not very knowledgeable about Windows: I really only do UNIX systems like Linux and MacOS. But since other parts of the system can't see it and it doesn't appear visible outside the task script I'm no longer sure. I thought it was, since when I run commands that modify the registry I get no errors and a query run in the task shows it's there. I don't know if the bamboo agent itself is running with elevated privileges or not. Well, the user account running the agent definitely can "run as administrator" (this is a dedicated bamboo agent host and there's only one user account on it, and I log in as that account and I can "run as administrator"). But, I can't seem to find any info about anything like this in the documentation. commands pretend to succeed while not actually modifying the registry at all? That's the only way I can explain the behavior I'm seeing.
Is there some magical thing that the Bamboo agent does that fakes out the Windows registry so that reg add / reg query / etc. And the HKLM settings still exist after the test concludes of course. Also, if I'm logged into the Windows system and I run the exact same test from a cmd.exe it works great with no errors: it finds the driver and the tests succeed. Then when I log into the Windows system and look at the registry, none of my HKLM settings exist (I purposefully didn't remove them again). However starting the ODBC client fails saying no driver is registered. When I do this (from a cmd.exe inline Script task) it succeeds with no errors and if I run reg query in my Bamboo task script, both before and after I run the client, I can see all the settings just as I want them.
#BAMBOO SOFTWARE WINDOWS 10 INSTALL#
In order to install the driver so it can be tested I need to modify the Windows registry HKLM (HKEY_LOCAL_MACHINE) section to add information about the driver DLL. One of the plans I want to create is for testing an ODBC driver.
#BAMBOO SOFTWARE WINDOWS 10 WINDOWS 10#
I have a Bamboo remote agent running on a Windows 10 server.
0 kommentar(er)
