Windows2003 remote install on x4100 server

I have purchased X4100 , I need to install windows2003 operating system through network.
I have configured RIS server.Configuration files and the disposition step is as follows
txtsetup.sif files:
[SourceDisksFiles]
lsi_sas.sys = 1,,,,,,3_,4,1
[HardwareIdsDatabase]
PCI\VEN_1000&DEV_0050 = "lsi_sas"
PCI\VEN_1000&DEV_0054 = "lsi_sas"
PCI\VEN_1000&DEV_005E = "lsi_sas"
[SCSI.load]
lsi_sas = lsi_sas.sys,4
[SCSI]
lsi_sas = "LSI Logic Fusion-MPT SAS Driver (Server 2003 32-bit)"
[Unattended]
OemPreinstall = yes
OemPnpDriversPath="\Sun\Drivers\adm\8111\hpet;\Sun\Drivers\amd\8131\ioapic;\Sun\Drivers\amd\8131\pcix;\Sun\Drivers\ami;\Sun\Drivers\lsi"
My question is :
X4100 can carry on the network installation,but X4100 Cannot start normally after reboot .
How will I solve it.

I am having the same issue, with a 64 bit build.
Textmode installation goes smoothly, as does the graphical portion. However when windows gets ready to boot for the first time, no disk is found.
I have opened a case with Sun as have received little help. I have followed Sun documentation to a T.
Need help!!

Similar Messages

If I were to purchase the Apple Remote Desktop with Unlimited licenses, would I be able to install the client software on each of there computers/laptops and have them remote desktop into the server?

I have several friends and family who are looking for a central place to access information from ( Pictures, home movies etc ). So I am considering setting up an OSX Lion Server. There are some other things I can use it for as well.
Here is my question:
If I were to purchase the Apple Remote Desktop with Unlimited licenses, would I be able to install the client software on each of there computers/laptops and have them remote desktop into the server? Or would I have to install the Admin software on each? Do they intend it to be used strictly as one admin to access many clients?
I always could set up a network drive so they can log in and just see the folders they have created with space on the server I provide them. But I want them to be able to log an and actually use it as a Remote Desktop.
Thanks,
Eric

Dave,
Thanks for the feedback. I understand that ARD is meant for Remote Administration, but I was not sure if it could be used for my purpose as well. The reason I was looking to do it this was was because I read several articles online about security and performance issues with setting up VNC and activating screen sharing. Unless I am misunderstood.
As far as people's activities on the server, mostly it is going to be used as a place for them to store their media. I will only allow own person ( Who I trust and I know wont botch the server ), to run applications. Everyone else will be restricted to uploading and downloading content to their designated account on the server as well as a community share on the server.
I appreciate your help.
Thanks,
Eric

2010 Mac mini server remote install OS X failure

I tested re-installing OS X remotely to my 2010 Mac mini server. It worked the first time. I got to the installation process, and abandoned it without actually doing anything.
But when I tried again, it failed, and I have not been able to get it to work ever since. I went to a local Apple shop and tested at its Genius bar. People there cannot figure out the problem. They exchanged my unit for a new one.
I took the new unit home, tried, and it failed again. Then I called Apple Care. They cannot pin-point the problem, but suspected that, since I failed with two units, the problem may be with the computer that has the DVD. I am not sure about his. Here I post my story for help. The details:
1. The OS X Server installation DVD (which came with the mini) was put in a 13" 2009 Macbook Pro. There I ran the Remote Install OS X application. Selected the Installation DVD.
2. Then I started the Mac mini server, holding the down Opt key. The Installation DVD appeared from my local network. However when I selected the DVD and clicked the arrow sign under it, things went wrong. A circle with a line segment appeared briefly (indicating a problem, I think). Then the mini simply went to boot from its own hard drive where the original OS X was.
Help and suggestions are very much appreciated.
Additional information:
Remote Disc works fine. From my Mac mini, after booting into the original OS, I can see and open DVDs in the Macbook Pro.

Target disk mode method works fine. I can boot my mac mini from its installation DVD placed in my macbook pro, connected to the mini through firewire. So I don't think there is any hardware problem.
I played with a few other things. First I used another DVD, this time the one that came with my 2009 macbook pro, a non-server version OS X. When I tried to remote install it to my mini, the mini can still see the DVD but it hung after I chose to boot from it. It just showed a big circle with a line segment. It did not revert to boot the OS on its own hard drive.
Next I again ran remote install on macbook, but booted the mini to its own hard drive. From there
I changed its start up disk to Network Startup, and rebooted. The mini can find nothing on the local network.

Why SCCM 20012 Install fails with remote 64 bit SQL Server but proceeds for remote 32 bit SQL Server

I have the following setup:
AD User accounts
- SQLAdmin (used to run SQL Services i.e. Database Engine)
- SCCMADmin (used to install SCCM 2012)
SPN registered for user account SQLAdmin
setspn -S MSSQLSvc/SQL.Domain_Name:1432 Domain_Naem\SQLAdmin
setspn -S MSSQLSvc/SQL:1432 Domain_Name\SQLAdmin
setspn -S MSSQLSvc/SQL.Domain_Name:1433 Domain_Naem\SQLAdmin
setspn -S MSSQLSvc/SQL:1433 Domain_Name\SQLAdmin
and checked with setspn -L TESTING\SQLAdmin
1 SERVER called SQL
32bit Server with SQL Server 2008 + SP3 + Cumulative Update 6
2 SQL instances - Default (MSSQLSERVER) and
SCCM2012
MSSQLSERVER instance uses TCP port 1433
SCCM2012 Instance users TCP port 1432 (no dynamic ports)
User accounts that have been given public and sysadmin SQL server roles
on both instances are: SQLAdmin, SCCMAdmin, Domain Administrator, Local Administrator and computer account SCCM
Client Protocols TCP enabled (and Named Pipes) (checked via SQL Server Configuration Manager)
Local Administrators Group on this server has members - SQLAdmin, SCCMAdmin, Domain Administrator, Local Administrator and computer account SCCM
Firewall turned on with access allowed on Ports 1432, 1433, 4022,445, and WMI - WMI-in, DCOM-in and ASync-iN builtin rules allowed\enabled.
1 SERVER called SQL3
64bit Server with SQL Server 2008 + SP3 + Cumulative Update 6
2 SQL instances - Default (MSSQLSERVER) and
SCCM2012
MSSQLSERVER instance uses TCP port 1433
SCCM2012 Instance users TCP port 1432 (no dymanic ports)
User accounts that have been given public and sysafmin SQL server roles on both instances are:
SQLAdmin, SCCMAdmin, Domain Administrator, Local Administrator and computer account SCCM
Client Protocols TCP enabled (and Named Pipes) (checked via SQL Server Configuration Manager)
Local Administrators Group on this server has members - SQLAdmin, SCCMAdmin, Domain Administrator, Local Administrator and computer account SCCM
Firewall turned off
1 SERVER called SCCM
64bit Server that is to be the Primary Site Server\MP for SCCM 2012
ODBC link to SQL\SCCM2012,1432
ODBC link to SQL3\SCCM2012,1432
ODBC uses SQL Native Client 10.0 (64 bit)
Both ODBC connections when TESTed pass and suggest connectivity to SQL Servers
Install process doe SCCM2012
Tried to install SCCM 2012 RC2 when logged in to SCCM Server as AD user account
SCCMAdmin, and when utilising the SCCM2012 SQL instance on
32 bit server of SQL install proceeds barring warning about 8GB rec, for SQL Server. Then fails on PKI certificate issue. Installation (chose HTTP for MP). I beleive the PKI failure as install starts is
due to the fact that SCCM 2012 needs its database server to b 64 bit ?
Thus i then tried to install SCCM 2012 RC2 when logged in to SCCM Server as AD user account SCCMAdmin, and
when using the SCCM2012 SQL instance on
64 bit server of SQL install proceeds but fails at checking stage and says:
SQL Server sysadmin rights FAILED SQL3.Domain_Name
Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions. Setup
cannot continue.
and
Site System to SQL Server communication WARNING SCCM.Domain_Name
A communication error has been detected between the specified site system and the site database computer. This error can occur when the site database server is offline or if a valid SPN has not been registered in Active Directory Domain Services for the SQL
Server instance hosting the site database. Setup cannot continue.
Why does the install of SCCM 2012 with 32 bit SQL proceed further than the install with 64 bit SQL, with the latter process failing as above error meesages show and yet both servers are set identically (apart from temporary turning off Firewall on the 64
bit server) and during the install the Databse Server specified is accepted ?

Thanks for the reply.
I can connect via ODBC to the the 32 bit SQL Server and the 64 bit SQL Server from the SCCM Server
The SQL Server Unit called SQL3 unit is a 64 bit SQL.
The SQL Server Unit called SQL is only 32 bit, but at least gets past the final checking stage and the error messages about sysadmin rights and Site System to SQL Server communication problem, and then fails with PKI certificate error message.
When trying to install SCCM specifying the 64 bit SQL Server as the Database Server it gives the 2 error messages at the final checking stage of the installation as listed.
So as I said what is confusing is the fact that if the SCCM install uses the remote 32 bit SQL Server it passes the final checking (although fails with PKI certificate message) but the 64 bit SQL Server set up exactly the same apart from the Firewall being
left off for the time being, fails at the final check stage with the 2 listed errors.
If I use a local 64 bit SQL Server the installation is fine.
Still would like to find out what cause the 2 issues for the remote 64 bit SQL Server, when ODBC seems fine, sysadmin rights have been given for the installer account and the SCCM computer account and SPNs have been set for the user account running the SQL
Services.

Cannot do a SL Server 10.6 remote install

Hi!
I'm a newbe to the server environment and came to a halt emediately in trying to learn. I follow the Mac OSX Server Essentials 10.6 book and the first step is to do a remote install from another computer to the server, in my case a Mac Mini.
I can initate the installation process, e g the Mini and my MBP is connected and I can use Remote Install to let the Super Drive in the MBP deliver data to the Minin Server via my Network Switch.
When that process is ready, the Mini server is supposed to show up in the Server Admin window on my MBP to let me coninue the remote install. But it will not show up in the Server Admin window.
I checked that the Mini is "visible" in the network and it is, I used Network Utillity to check.
I done it from scratch several times but the Mini server will not show up in Server Admin on my MBP.
What am I doing wrong?
Smigge

Mac OS X Server requires a static IP address, and functional DNS. Full stop.
Unless you have sufficient public static IP addresses for your network (or if you're fully running IPv6), you'll be using private IP addresses and private DNS services.
You'll likely want to set up in a subnet in 10.0.0.0/8 or 172.16.0.0/12, and out of 192.168.0.0/16, as you'll eventually want VPNs, and VPNs depend on IP routing, and coffee shops and home networks tend to be in a few subnets in 192.168.0.0/16, and having the same subnet on both ends of the VPN makes for routing problems. Best not to start out with a subnet that can cause issues later.
Unless you're running public IP, you'll want to [set up your own DNS services|http://labs.hoffmanlabs.com/node/1436].
SRV records are generally unnecessary.
I'm here presuming you're not doing public-facing mail; that adds some complexities here.

Sap4.7 and sql server 2000 on windows2003:when install di ,error:MDB-05039

sap4.7 and sql server 2000 on windows2003:
when install database instance ,there is a error,at change tempdb
MDB-05039:Unable to stop server dev ,
please help !!!!

Every time you start SQL Server it also creates a new tempdb. When you change the layout (physical structure, size) you have to restart SQL Server in order for these changes to take effect.
It seems that the installation routine has changed the layout (it does that according to your input!) and is now trying to stop and restart SQL Server. When you run into this error, have you tried to stop and restart SQL Server manually? After that choose the Retry option of the installation routine. Just a guess...
Do you have some more log information?
Sven

I am trying to remote into a Windows Server 2003 from a Windows 7 machine and having issues

I am trying to remote into a Windows Server 2003 from a Windows 7 machine. It says "The terminal server has exceeded the maximum number of allowed connections".
My first stop in trying to solve this problem was here:
[URL="http://www.howtogeek.com/howto/windows/command-line-hack-for-terminal-server-has-exceeded-the-maximum-number-of-allowed-connections/"]howtogeek.com[/URL]
And it says:
[I]
[INDENT]This problem happens because Windows only allows two remote terminal services connections when you are in administrative mode, and you’ve either got two people already on that server, or more likely, you’ve got a disconnected session that still thinks
it is active.
The problem with this error is that you have to actually get on the server console to fix the problem if the server isn’t in a domain. ([B]If you are in a domain, then just open Terminal Services Manager and log off or disconnect the sessions[/B])[/INDENT][/I]
So it seems to suggest that all I have to do really is to run the Terminal Services Manager but I cannot find it.
This web site from mssqltips.com [URL="http://www.mssqltips.com/sqlservertip/1981/remote-desktop-error-terminal-server-has-exceeded-the-maximum-number-of-allowed-connections/"](click here)[/URL] says all I need to do is first execute "mstsc /
admin" from the command line. But, when I do that, I get a message when I try to remote to the server, that says this: "To log on to this remote console session, you must have administrative permissions on this computer".
So, what now? What do you suggest?

Hi Bobby,
Yes, it is by design. By default, Windows Server only accepts two concurrent administrative sessions (Administrative Mode). It means that only two administrators can work on the server at
the same time.
If you would like more concurrent sessions, you need to purchase RDS CALs, install Terminal Services related server roles with proper configurations on the server.
Remote Desktop for Administration (server 2003)
http://technet.microsoft.com/en-us/library/cc785186(v=ws.10).aspx
What Is Terminal Services?
http://technet.microsoft.com/en-us/library/cc782486(v=ws.10).aspx
Terminal Services Configuration
http://technet.microsoft.com/en-us/library/cc787078(v=ws.10).aspx
Purchase client access licenses
http://technet.microsoft.com/en-us/library/3660ac5a-7468-48d3-b7e8-5529de8fb6c5
Thanks.
Jeremy Wu
TechNet Community Support

Remote Install Failure on AIA3.0

Hi,
Remote Install Failure on AIA 3.0:
AIA 3.0 installations on Windows XP-Pro is failing in Step 4 of 11 with the Error
"Node manager is down or the username and password entered is incorrect"
Details on the installation are as follows:
1) Installation is done on a Windows-XP 32 bit SP2, RAM - 4 GB.
2) SOA Suite 11gR1 PS1 and Weblogic 10.3.2 successfully installed.
3) SOA managed server, Admin server and node manager are running successfully on remote server.
4) The status of Node manager is reachable and has been confirmed through the admin console.
5) When installing AIA 3.0 use Remote Install option, the 4th step is failing after providing the node manager credentials of remote server.
Error message is "Node manager is down or the username and password entered is incorrect".
6) We given remote server configuration on 4th step (Host Name, Admin Port, Domain name, user/pass).
7) The Remote WLS Server is reachable.
8) Installer is always looking local node manager is not looking for Remote node manager which one is running on remote machine.
Error Log
Adding C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM for deletion.
Adding to classpath:file:/C:/WINNT/TEMP/OraInstall2010-04-29_04-25-49PM/ext/jlib/soawl.jar
Adding to classpath:file:/C:/WINNT/TEMP/OraInstall2010-04-29_04-25-49PM/ext/jlib/template.jar
null
configFileName:C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\footprint.xml
osName:Windows XP
Inside startPreReqOperation...prereq
osName:Windows XP
diskSpaceRequirements from engine:Home id =SoftwareOnlyOraclehome name=Oracle home variable=%AIA_HOME_PATH% fixedSpace=2048 unit=MB condition=null totalSpaceRequired=0 isConditionSatisfiedfalse
entryPoint: entryPoint = oracle.installType.all condition = null className = null
contextFile:C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\prereq\oui\agent_prereq_context.xml
The entry point is: oracle.installType.all
Check Name:CertifiedVersions
Check Description:This is a prerequisite condition to test whether the Oracle software is certified on the current O/S or not.
Expected result: One of 5.1,5.2,6.0,6.1
Actual Result: 5.1
Check complete. The overall result of this check is: Passed
Check Name:ServicePackChecks
Check Description:This is a prerequisite condition to test whether the Service Pack level recommended for installing the product is available on the system.
Expected result: 2
Actual Result: 2
Check complete. The overall result of this check is: Passed
Check Name:TotalMemory
Check Description:This is a prerequisite condition to test whether the system has sufficient physical memory.
Expected result: 1024MB
Actual Result: 3191MB
Check complete. The overall result of this check is: Passed
Property File location: D:\AIA3.1\New Folder\cd\Disk1\install\win32\aiaoneclick.properties
Item State: javax.swing.JComboBox[,170,52,262x18,invalid,layout=com.jgoodies.looks.plastic.PlasticComboBoxUI$PlasticComboBoxLayoutManager,alignmentX=0.0,alignmentY=0.0,border=,flags=4194632,maximumSize=,minimumSize=,preferredSize=,isEditable=true,lightWeightPopupEnabled=true,maximumRowCount=8,selectedItemReminder=AIA3]
Path: D:\Oracle11GPS\Oracle\Middleware_new\AIA3
Item State: javax.swing.JComboBox[,170,81,262x18,invalid,layout=com.jgoodies.looks.plastic.PlasticComboBoxUI$PlasticComboBoxLayoutManager,alignmentX=0.0,alignmentY=0.0,border=,flags=4194632,maximumSize=,minimumSize=,preferredSize=,isEditable=true,lightWeightPopupEnabled=true,maximumRowCount=8,selectedItemReminder=D:\Oracle11GPS\Oracle\Middleware_new\AIA3]
Home: AIA3
In processFieldStringAIA Home
In processFieldStringJAVA HOME
In processFieldStringAIA Home Path
In processFieldStringAIA Instance Name Contains invalid characters
getting root directory
D:\oracle11GPS\Middleware\user_projects\domains\dev_domain
truevalue for type of install
D:\Oracle11GPS\Oracle\Middleware_new\jdeveloper
D:\Oracle11GPS\Oracle\Middleware_new
*****Web Logic Home: D:\Oracle11GPS\Oracle\Middleware_new\wlserver_10.3
CLASSPATH: D:\Oracle11GPS\Oracle\Middleware_new\wlserver_10.3\server\lib\weblogic.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM;;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\adapters.xml;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\adf-config.xml;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\aqapi.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\bpelImport.log;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\ccrQueries.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\com.bea.cie.comdev_6.1.0.0.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\com.bea.cie.config_6.0.0.0.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\com.bea.core.common.security.api_1.0.0.0_5-1-0-0.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\com.bea.core.nodemanager.plugin_1.3.0.0.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\commonutils.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\connections.xml;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\dms.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\emocmutl.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\encrypt.bat;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\encrypt.sh;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\engine.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\enginehelp.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\footprint.xml;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\glassfish.jaxb.xjc_1.0.0.0_2-1-7.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\glassfish.jaxb_1.0.0.0_2-1-7.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\harvest-tasks.xml;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\harvest.bat;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\harvest.sh;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\harvester-10.3.1.0.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\harvester-ant.xml;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\harvesterSettings.xml;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\install.properties;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\jython-modules.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\log-config.xml;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\log4fl.properties;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\message.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\ojdbc5.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\ojdl-log4j.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\ojdl.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\ojdl2.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\oneclick.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\oneofftool.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\runant.bat;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\runant.sh;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\setenv.bat;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\setenv.sh;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\soainstallhelp.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\soawl.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\SysInfo.dll;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\template.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\tools.xml;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\tools11g.xml;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\types.properties;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\wlcipher.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\wlfullclient.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\wtinstallhelp.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\xml.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\ext\jlib\xmlparserv2.jar;;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\OraInstaller.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\oneclick.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\xmlparserv2.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\share.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\OraInstallerNet.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\emocmutl.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\emCfg.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\OraPrereq.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\jsch.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\ssh.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\remoteinterfaces.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\http_client.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\OPatch\jlib\opatch.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\OPatch\jlib\opatchactions.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\OPatch\jlib\opatchprereq.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\OPatch\jlib\opatchutil.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstImages.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstHelp.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstHelp_de.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstHelp_es.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstHelp_fr.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstHelp_it.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstHelp_ja.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstHelp_ko.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstHelp_pt_BR.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstHelp_zh_CN.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\InstHelp_zh_TW.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\oracle_ice.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\help4.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\help4-nls.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\ewt3.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\ewt3-swingaccess.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\ewt3-nls.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\swingaccess.jar;\;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\jewt4.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\jewt4-nls.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\orai18n-collation.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\orai18n-mapping.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\ojmisc.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\xml.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\srvm.jar;C:\WINNT\TEMP\OraInstall2010-04-29_04-25-49PM\oui\jlib\classes12.jar
1
localhost
LocalMachine
Connecting to Node Manager ...
<Apr 29, 2010 4:31:11 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
Either the password and username entered are incorrect or the node manager is down
Traceback (innermost last):
File "<string>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 618, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : I/O error while reading domain directory
Use dumpStack() to view the full stacktrace
Anyone knows how to install AIA Remote Install on the remote SOA server?

Hi,
may be you enter the wrong username or password? Or there is a problem with certificate? The look file describe a wrong user name or password or nm is not reachable. Is it possible to start managed server via Admin Console? Please check nm log files.
Regards,
Marcel

Can 2 Macs connect with ethernet cable to share DVD for remote install?

Can I simply connect a Mac Mini Server and MacBook together with an ethernet cable?
I want to reinstall Mac OS X Server on the DVDless Mac Mini. There is no separate AirPort device.
So do I just connect the two machines with an ethernet cable, start the remote install program on the MacBook, then restart the Mac Mini with the Option key pressed?
Thanks.

According to page 57 of the Getting Started 10.6 server manual, you can use a Mac with a DVD drive operating in target disk mode for this. I see no mention of using Ethernet so I assume it is not supported. Even if it was, it would be extremely slow compared to using FireWire target disk mode.

The grace period for the Remote Desktop Session Host server has expired

<p>I'm running Windows Server 2012, we only have 1 server and it's a DC. I'm trying to RD to the server from my Windows 7 laptop. It was working fine on Friday but when I came in on Monday I got message saying that 'The remote session was disconnnected
because there are no Remote Desktop License Servers available to provide a license'
So after a bit of digging I found out my 'grace period' had expired, so ordered a new license which I got today, installed this all ok but still i cannot connect via RD I get the same message....went into the RD License Diagnoser and it said the problem
was as follows
'The grace period for the Remote Desktop Session Host server has expired, but the RD Session Host server has not been configured with any license servers. Connections to the RD Session Host server will be denied unless a license server is configured for
the RD Session Host server.'
Suggested Resolution as follows
Configure a license server for the Remote Desktop Session Host server. If you have an existing license server, specify that license server for the RD Session Host Server. Otherwise, install RD Licensing on a computer on your network and Configure RD Session
Host Server to use it.'
I cannot figure out how to do this as I cannot find the RD Session Host Server tool.
Can any of you lovely people help me please

Hello,
Best option would be to assign the license server by using AD GPO. Youl will need to configure the following:
Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Licensing
and define the settings for:
Use the specified Remote Desktop License Server
Set the Remote Desktop Licensing mode
Then assign the policy tho your server.
regards Robert Maijen

How to Configure Remote Connections To SQL Server 2008 R2 Express

Post written June 10, 2010 and pertains to:
SQL Server 2008 R2 Express on both my server and local machines: SQLX_SRV,
SQLX_LOC
SQL Server 2008 R2 Management Studio on both my server and local machines:
MS_SRV, MS_LOC
Windows Server 2008 R2 Enterprise installed on a Hyper-V VPS: WS
SQL Server Configuration Manager on both my server and local machines:
CMGR_SRV, CMGR_LOC
Server Manager: SMGR
I am connecting to my hosting server via Remote Desktop Connection: RDC
I installed SQLX_SRV and MS_SRV on my hosting server and SQLX_LOC and MS_LOC on my local development machine. I am able to use MS_LOC to connect to SQLX_LOC and to use MS_SRV to connect to SQLX_SRV. However I am not able to use MS_LOC to connect
with SQLX_SRV. Here's what I have done so far:
SMGR -> Configuration -> Windows Firewall to turn off the Windows Firewall for Domain, Private and Public profiles. Obviously I'll change this later, but until I can connect I want to remove as many variables as possible.
CMGR_SRV -> SQL Server Services to confirm that both SQL Server (SQLEXPRESS) and SQL Server Browser services were running.
CMGR_SRV -> SQL Server Network Configuration -> Protocols for SQLEXPRESS to ENABLE the Shared Memory, Named Pipes, and TCP/IP protocols and DISABLE the deprecated VIA protocol.
CMGR_SRV -> SQL Server Network Configuration -> Protocols for SQLEXPRESS -> double click TCP/IP to open the TCP/IP properties dialogue. On the Protocol tab Enabled: Yes, Keep Alive: 30000, changed Listen All to No. I've tried it both
ways, but I've got six IP addresses on my server and I wanted to configure SQLEXPRESS to listen to only the first and primary IP. On the IP Addresses tab went to IPALL and cleared the TCP Dynamic Ports field and entered 1433 in the TCP Port field.
For my first and primary IP Address I made sure that Enabled was Yes, I cleared the TCP Dynamic Ports field, and entered 1433 in the TCP Port field. For all other IP Addresses Enabled was set to No and I cleared both the TCP Dynamic Ports and TCP Port
fields.
CMGR_SRV -> SQL Server Services -> SQL Server (SQLEXPRESS) right click and Restart. This of course stopped and restarted my instance of SQLX_SRV enabling the TCP/IP configuration in the previous step to take effect.
On my server, SQLX_SRV is the only instance of SQL Server running and so it's easy to hard wire it to the default port 1433.
The instance name for both SQLX_SRV and SQLX_LOC is the default "SQLEXPRESS". My server machine name is "SERVER1" on the EnglishBrains.com domain. So the proper local name (local within the context of my remote server as connected via RDC) for
my instance of SQLX_SRV would be:
SERVER1\SQLEXPRESS
Note the use of a backslash NOT a forward slash.
Of course to connect remotely from my development machine, which is not on the same domain as my hosting server, I would need to specify the domain as well, so the SQL Server name becomes:
SERVER1.EnglishBrains.com\SQLEXPRESS
I must also use SQL Server Authentication. Before I can use such a remote connection, however, there are still several configuration steps required. So on my server (connected via RDC) I used MS_SRV to connect to SQLX_SRV using SERVER1\SQLEXPRESS
for the server name and Windows Authentication. Once connected I performed the following steps:
MS_SRV -> right click the connected parent SERVER1\SQLEXPRESS instance node at the top -> Properties -> Security -> Server authentication: select "SQL Server and Windows Authentication mode". This will enable connections using either type
of authentication.
Next, leaving the Server Properties dialogue open, Connections -> check "Allow remote connections to this server" box.
Click OK to save these changes and close the Server Properties dialogue.
MS_SRV -> Security -> right click Logins and select "New Login...", the Login - New dialogue opens.
On the General page Enter a name for your new login
Select SQL Server Authorization
Enter and confirm a password
Uncheck Enforce password expiration
Select the default Database and Language
On the ServerRoles page Public will be checked, also check SysAdmin. This is probably not a good idea and I'll uncheck this as soon as I can connect to the SQLX_SRV.
On the User Mapping page select the databases you want your new Login to access and enter the Default Schema of "dbo".
At the bottom of the User Mapping page you'll see the Database Roles table. Public will be selected by default. Also select db_Owner. Again this is probably not a good idea, and I'll refine this once I can connect.
On the Status page confirm that "Grant" is checked under "Permission to connect to database engine" and "Enable" is checked under "Login".
Click OK to save all changes and close the Login - New dialogue.
With these steps completed you should now be able to use MS_SRV to connect to SQLX_SRV using SQL Server Authentication by supplying the name and password for your new Login. I tried this and it worked fine. Next I tried to use this same login
remotely, that is I went to my local development machine and used MS_LOC to try and connect to SQLX_SRV by using
SERVER1.EnglishBrains.com\SQLEXPRESS
and opting for SQL Server Authentication and supplying the name and password of my new login.
THIS DID NOT WORK?? Instead I get the following error message:
Cannot connect to SERVER1.EnglishBrains.com\SQLEXPRESS.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click:
http://www.microsoft.com/products/ee/transform.aspx?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1
If you follow the suggested help link, you are told:
The SQL Server client cannot connect to the server. This error could be caused by one of the following reasons:
A specified SQL Server instance name is not valid.
The TCP, or named pipes protocols are not enabled.
The firewall on the server has refused the connection.
The SQL Server Browser service (sqlbrowser) is not started.
WRONG on all 4 counts! The instance name IS valid. Both TCP/IP and Named Pipes protocols are enabled. The firewall has been shut down, so it is not relevant. Finally the SQL Server Browser IS started.
The next thing I tried was to circumvent discovery by the SQL Browser service by using the following syntax to specify the IP address and port directly when specifying the SQL Server name.
tcp:68.71.134.186,1433
Using this in the Server Name field I was able to use MS_SRV to successfully connect to SQLX_SRV (using SQL Server Authentication of course) with or without the SQL Browser service running.
However when I tried to connect from MS_LOC to SQLX_SRV using this same login (WITH SQL Browser service running just for good measure) it does not work?? I get the following error message:
Cannot connect to tcp:68.71.134.186,1433.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476
If you follow the help link you are told:
"The SQL Server client cannot connect to the server. This error could occur because either the firewall on the server has refused the connection or the server is not configured to accept remote connections."
However, the firewall has been shut down and the server HAS been configured to accept remote connections!
I confirmed that i could indeed Ping to 68.71.134.186 and running NetStat -a |find /i "listening" on the server shows that the server is indeed listening at 68.71.134.186 Port 1433 -- which is why I was able to connect to SQLX_SRV using MS_SRV with
tcp:68.71.134.186,1433 .
IN SUMMARY: Even though I can connect to my SQLEXPRESS instance multiple ways from the server itself, I cannot connect remotely from my development machine!
If anyone can help me figure out why I would be very, very grateful!

My two cents to help you out on c# code example to configure the remote sql server express.
Hope it helps. It works, but you have to be extra carefull to read it all and setup the server configuration and netsh commands; also the port fowarding on the router.
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Data.SqlClient;
namespace sqlremoteconnection
class Program
static void Main(string[] args)
// this is the local sql server connection
// 192.168.1.101\SQLEXPRESS
// now, the configuration for remote access:
// activate SQL SERVER BROWSER - set it to start "automatic"; then START UP
// SQL Server Configuration Manager
// --> SQL SERVER BROWSER -> properties -> Service -> Start Mode -> automatic -> apply
// --> Log On -> Start -> Ok
            // netsh firewall set portopening protocol = TCP port = 1433 name = SQLPort mode = ENABLE scope = all profile = CURRENT
            // netsh firewall set portopening protocol = UDP port = 1434 name = SQLPort mode = ENABLE scope = all profile = CURRENT
            // netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action = allow localport = 1433 remoteip = any profile = PUBLIC
            // netsh advfirewall firewall add rule name = SQLPort dir = in protocol = udp action = allow localport = 1434 remoteip = any profile = PUBLIC
// VERY IMPORTANT FOR REMOTE ACCESS: you have to add the rules on port fowarding
// on the router!!!
// TCP: 1433
// UDP: 1434
// or just a personal port like TCP 31433/UDP 31434
// read carefully the netsh commands above
// server name: 123.132.24.177\SQLEXPRESS
// server name: anyurl.myftp.org\SQLEXPRESS,1433 <<-- regular port
// server name: anyurl.myftp.org\SQLEXPRESS
// server name: anyurl.myftp.org\SQLEXPRESS,31433 <<-- WOW different PORT here!!!
SqlConnection myConnection = new SqlConnection(
"user id=sa;" +
"password=password_goes_here!;" +
"server=anyurl.myftp.org\\SQLEXPRESS,31433;" +
//"Trusted_Connection=no;" +
"database=database_name_here; " +
"connection timeout=30");
try
myConnection.Open();
catch (Exception e)
Console.WriteLine(e.ToString());
try
SqlDataReader myReader = null;
SqlCommand myCommand = new SqlCommand("select * from mytable", myConnection);
myReader = myCommand.ExecuteReader();
while (myReader.Read())
Console.WriteLine(myReader["tab01_name"].ToString());
Console.WriteLine(myReader["tab01_age"].ToString());
catch (Exception e)
Console.WriteLine(e.ToString());
try
myConnection.Close();
catch (Exception e)
Console.WriteLine(e.ToString());
Adelino Araujo

Not able to access database from a remote machine using SQL Server Management Studio

Hi,
I have a DB_BOX with SQL Server 2008 R2 installed. I can access the databases on the local machine using SQL Server Management Studio but it is not accessible from other machines, though the machines are in same domain.
I have remote enabled on SQL Server box, TCP enabled, firewall off. I checked with IP Address too, all SQL Server services are running.
The SQL Server log shows the message
The requested service has been stopped or disabled and is unavailable at this time. The connection has been closed.
I get the below message in SSMS from remote machine.
Details of error message are
===================================
Cannot connect to DB_BOX.
===================================
A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=64&LinkId=20476
Server Name: DB_BOX
Error Number: 64
Severity: 20
State: 0
Program Location:
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
   at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket()
   at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
   at System.Data.SqlClient.TdsParserStateObject.ReadByte()
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
   at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
   at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

Sorry, missed the message from the errorlog in the original post. You shouldn't have included that big .Net dump that hid the important facts. :-)
My first Google attempt on that message (which I have never seen before) suggests that the TCP Enpoint is stopped, so try this:
ALTER ENDPOINT [TSQL Default TCP]
STATE=STARTED;
Erland Sommarskog, SQL Server MVP, [email protected]
This solves the problem. Thanks...

Please help me with the step by step instructions on how to install a Windows server 2008 on a computer that has Windows 8 installed on it

Please help me with the step by step instructions on how to install a Windows server 2008 on a computer that has Windows 8 installed on it without formatting windows 8.Please email the steps , Thanks

Please help me with the step by step instructions on how to install a Windows server 2008 on a computer that has Windows 8 installed on it without formatting windows 8.Please email the steps , Thanks
Assuming your rig can support virtual machines, you can use Hyper-V and run another OS there.
Better practice however is to use a dedicated machine and use remote desktop to the server.
Corsair Carbide 300R with window
Corsair TX850V2 70A@12V
Asus M5A99FX PRO R2.0 CFX/SLI
AMD Phenom II 965 C3 Black Edition @ 4.0 GHz
G.SKILL RipjawsX DDR3-2133 8 GB
EVGA GTX 6600 Ti FTW Signature 2(Gk104 Kepler)
Asus PA238QR IPS LED HDMI DP 1080p
ST2000DM001 & Windows 8.1 Enterprise x64
Microsoft Wireless Desktop 2000
Wacom Bamboo CHT470M
Place your rig specifics into your signature like I have, makes it 100x easier to understand!
Hardcore Games Legendary is the Only Way to Play!

How do I directly install Mountain Lion Server?

I'd like to upgrade my Lion Mac Mini Server to Mountain Lion. Currently I'd have to update it to 10.8 Client, then on the server, install the Server app. Is there anyway to consolidate those two steps into one? I'd like to directly install 10.8 Server so I could perform remote setup of the server in one step. Is that possible?

From what I understand, you would need to update the OS X Lion Server to the 10.8 Client version followed by the OS X 10.8 Server Add-on. I am not too sure if Apple is providing an unified step for this kind of procedure.

How to monitor MySQL Server installed in Windows Server using Nagios

You can do this via NSClient as Gary posted. The NSClient is a communications system that allows nagios to send commands to a target system over the nsclient protocol and they are executed on the remote system. You will still have to build some kind of vbscript or plugin to run on the target system to do the actual query to check on mysql.There are other options to. If you enable snmp on your target computer you can use a few nagios plugins to query the snmp agent on the target computer to see if a service is running. To do this via snmp you will need this plugin "check_snmp_process.pl" fromthis site.Your check command will look something like this:check_win_process:= check_snmp_process.pl -H $HOSTADDRESS$ -C "$USER6$" -n "$ARG1$" -w $ARG2$ -c $ARG3$The service definition will be like this:check_win_process!sqlservr!0!0This will check...

I installed Nagios Core in my Ubuntu workstation 10.04 for me to learn something new in my craft. I use this now to monitor our Windows Server 2008 with MySQL server installed as well as our Datalink Switch (DGS-1210-24). I searched on google on how to monitor a MYSQL server installed in Windows server using Nagios Core but i could not seem to find any. Could anybody who's expert in Nagios give me steps on how to do so. Thanks. All i found in google were steps in monitoring mysql installed in linux and nothing in windows server.
This topic first appeared in the Spiceworks Community

Windows2003 remote install on x4100 server

Similar Messages

Maybe you are looking for