When using an Amazon Web Services RDS instance from a Java application, what is the best JDBC connection string? It should tolerate the instance falling over to the standby. AWS handles flipping the CNAME to point from the primary to standby under the hood.
When I create a scheduled task, I do so via command line:
schtasks.exe /Create /TN "startup-script" /TR "C:\startup.bat" /RU taskuser
/RP taskpasswd /SC ONLOGON
The idea is that this task run forever. The batch opens a java process that is never meant to end.
I've used ONLOGON, as the machine auto-logs in as taskuser.
All this works fine, for about 72 hours, after which the Duration flag kicks in and ends the process. Windows XP doesn't have the /DU flag on command line - is there an alternative method to creating a task that is meant to run from a system startup (doesn't even require logon) and runs forever, without touching a GUI?
I have an ESX host with 32 GB of RAM.
Placing three VMs on it, allocating each one to 16 GB RAM each - knowingly overcommitting the total.
Each VM has two network interfaces.
The first connects to a virtual switch called frontend and has an uplink NIC to a physical network.
The second connects to a virtual "switch-in-a-box" - i.e. no physical uplinks for this switch, and we call this network backend.
When the three machines are under load, the ESX vmkernel begins to swap some RAM out to disk - up to 6.5GB.
I cannot find any documentation/reasoning in regards to the backend network's performance degrading due to the heavier load due to memory swapping, but that is basically the impact.
Is there any clear reference regarding virtual switch speeds without any uplinks?
Trying to figure out if there is an environment variable or another method to get a given machine's logon domain from simple command line script.
The variable %USERDOMAIN% will provide me with the domain my user is - and in a domain trsut scenario does not return the machine's domain, rather MY domain.
The idea is that I want to be able to have my cmd script code not care about what domain it is in, but sitll be able to determine that info at runtime.
There's VBScript method here:
Set objRootDSE = GetObject("LDAP://RootDSE")
strDomain = objRootDSE.Get("DefaultNamingContext")
WScript.Echo strDomain
Another method is this:
net config workstation | findstr /C:"Workstation domain"
which outputs:
Workstation domain DOMAINNAME
But since there is no command line equivalent to unix cut, I am finding it difficult to get this info into a variable.
I saw this: How to redirect root and only root via htaccess? and it's close, but not quite.
I am in the middle of rewriting a site, and would like to be able to send users from:
http://myfullurl.com
to:
http://mylandingpageurl.com
While retaining the ability to test the site at:
http://myfullurl.hostingprovider.com
My AD domain is setup at:
mydomain.net
DNS is hosted on DCs for this namespace as well.
I have a couple of machines that live in namespace:
sub.mydomain.net
The DNS service for this subdomain is not hosted on a DC/Windows box.
I'd like to join these machines to the DC in mydomain.net - and retain their DNS namespace and identity.
How would one go about doing that?
We want to rename the machine and preserve all performance data in the SQL Server on the VirtualCenter.
What procedure would you recommend? DNS updates/changes, SQL statements and service console commands.
Using ESX 3.5 U4, logging on to the Web Access with FireFox 3.
Can't use the xPI console plugin.
Has anyone been able tog et this to work? I know that OSX/FF is not supported, but maybe someone's modified the xpi installer in some fashion?
Our corp site lives on top of Joomla 1.5.3.
In order to secure the administrative access, we implemented a redirect that when asking for the admin login page, you are redirected to the same URL, via SSL (http://site/administrator --> https://site/administrator )
Everything seems to work just fine, login and admin session is encrypted, but when running the extPlorer extension, the left sidebar loads, the main frame sticks at "Loading..." for ever.
Removing SSL redirection works fine, but isn't what we desire.