As I understand an Intel vPro based computer can be powered on remotely without the use of a 'magic packet', the management controller is sitting in a low powered state listening on specific ports. Therefore I'm assuming that the management controller is sharing the IP address of the host that is shut down.
Does the management controller maintain this IP address continually renewing it after the lease expires?
I'm trying to create network printers using a Powershell script. The script below creates the port without any issues, but will not create the queue. Can you anyone confirm if this script works on Windows Server 2008? (Note, you need to have the driver installed in order for this to work).
function CreatePrinterPort {
Param (
[string]$IPAddress
)
$port = [wmiclass]"Win32_TcpIpPrinterPort"
$newPort = $port.CreateInstance()
$newport.Name= "IP_$IPAddress"
$newport.SNMPEnabled=$false
$newport.Protocol=1
$newport.HostAddress= $IPAddress
Write-Host "Creating Port $ipaddress" -foregroundcolor "green"
$newport.Put()
}
function CreatePrinter {
Param (
[string]$PrinterName,
[string]$DriverName,
[string]$IPAddress,
[string]$Location,
[string]$Comment
)
$print = [WMICLASS]"Win32_Printer"
$newprinter = $print.createInstance()
$newprinter.Drivername = $DriverName
$newprinter.PortName = "IP_$IPAddress"
$newprinter.Shared = $true
$newprinter.Sharename = $PrinterName
$newprinter.Location = $Location
$newprinter.Comment = $Comment
$newprinter.DeviceID = $PrinterName
Write-Host "Creating Printer $printername" -foregroundcolor "green"
$newprinter.Put()
}
CreatePrinterPort -IPAddress "Localhost"
CreatePrinter -PrinterName Print1 -DriverName "HP LaserJet 4" -PortName "Localhost"`
-Location "Office" -Comment "Test comment"
The error I'm getting is on the CreatePrinter function:
Exception calling "Put" with "0" argument(s): "Generic failure "
Can anyone get uptime.exe to run either the /s or /p:n switches on a Windows Server 2008 box without crashing?
I realise it's a NT tool and no longer supported, but it worked fine on 2003. I've heard there's a version included in Server core, so I was wondering if that works better on 2008?
If uptime.exe is a no go, what do you use instead to get the system availability history?
It was my understanding that it's per process, not the total processes. But according to Large memory support is available in Windows Server 2003 and in Windows 2000 (KB283037):
Typically, a process running under Windows 2000 or Windows Server 2003 can access up to 2 GB of memory address space (assuming the /3GB switch was not used) with some of the memory being physical memory and some being virtual memory. The more programs (and, therefore, more processes) that run, the more memory you commit up to the full 2 GB of address space.
That to me says the more programs you run the more chance you will hit the 2GB address space limit i.e. Program A uses 500MB, Program B uses 1GB, so you've only got 500MB of address space for the rest of your programs.
However an MSDN article http://msdn.microsoft.com/en-us/library/ms189334.aspx refers to this as Process Address Space and to me implies that each application gets its own address space, be it 2GB or 3GB, depending what switch is being used in the boot.ini.
So is it per process or total process? And is the knowledge base article wrong (or badly worded)?
(Please note I'm talking about 32-bit systems only)
I'm looking to implement Ultrasound to monitor FRS in AD. I've a few questions around database permissions that I need answered before I deploy. I have no access to the SQL environment, therefore need to request everything up front.
Thank you