O R G A N I C / F E R T I L I Z E R: 10.08

Oct 27, 2008

jalasoft and savision – that’s great teamwork…

i just got this press release.  i have to say, this is great stuff!  unless you’re near an “envisioning center” it’s really difficult to get a grasp of how all these partner products work together to form a cohesive monitoring platform with operations manager.  here’s a little blurb about it…

Jalasoft and Savision team up at Microsoft Tech·Ed IT Professionals 2008

Santa Clara/Utrecht, October 27, 2008--

Jalasoft and Savision
announced today that they are teaming up to provide demonstrations of their products at TechED IT Professionals 2008 this November in Barcelona.  Jalasoft’s Xian Network Manager Io and Savision’s Live Maps are both products designed to work with Microsoft System Center Operations Manager 2007. Live Map’s elaborate mapping features give Xian users the power to create network aware topologies, business process and geographical maps of your network. Additionally, Xian Network Manager adds network devices down to interface level allowing you a detailed view of your topology so you can pinpoint exactly where the problem is located.

“Xian Network Manager provides data and alerts; Live Maps brings it all together into an easy to understand graphical representation” said Dennis Rietvink CEO at Savision, “Customers who combine these two products with Operations Manager 2007 will be astonished by the visualization power.”

Jalasoft and Savision can be found at booth E6 and E7 at Tech·Ed IT Professionals which takes place November 3 – 7, 2008 in Barcelona, Spain.

For more information contact:
Claudia Ricaldez, Claudia.Ricaldez@jalasoft.com, +1 888 402 6717

About Jalasoft
Jalasoft provides advanced systems management solutions for the heterogeneous computing environment. Xian Network Manager Io, in combination with Microsoft System Center Operations Manager or Microsoft System Center Essentials, is designed to proactively monitor and manage critical infrastructure components such as network devices and UNIX servers to increase availability and accelerate problem detection and resolution with the objective of improving the ROI customers realize from their infrastructure.

About Savision
Savision provides advanced visualization solutions for Microsoft’s System Center Operations Manager. Savision’s Live Maps allows IT Pros to quickly create monitoring maps that visualize business processes, network and service topologies, executive dashboards and geographical maps. Founded in 2006, Savision is headquartered in the Netherlands and is privately held. Savision’s founders and executives bring years of enterprise systems and application management experience from large IT service companies. For more information, go to
http://www.savision.com.

southeast management user group – november 14, 2008!

hey folks,

we’ve finished planning another user group and have the presenters and sponsors lined up.  acresso and securevantage were kind enough to buy us some food!  please make sure to register soon so we can get an accurate headcount to feed everyone.  :)

head over to the official smug site for the agenda, located at: http://systemcenterusergroup.com/blogs/smug/

if you just want to register, here’s the link: http://msevents.microsoft.com/CUI/InviteOnly.aspx?EventID=5B-11-D1-1D-08-92-D8-84-78-E1-CD-6A-5C-13-92-AA&Culture=en-US

 

look forward to seeing you all!

Oct 6, 2008

ping sweeping with FOR statements …

i just wanted to familiarize myself with the for statement in powershell by playing around with a few examples.  this one, i find particularly useful in situations where for example, i’m sitting in a lab and need to know what IPs are available.

back to what i was saying, to get familiar with the for statement, i thought i’d start off with what i know in cmd shell.  if you look at this this block below, you’ll see that i’m using the /L switch of the for statement to handle stepping through a sequence of numbers.

for /l %i in (1,1,255) do @ping -n 1 99.206.102.%i | find /i ": bytes=" > nul && @echo Successfully pinged 99.206.102.%i Successfully pinged 99.206.102.2 Successfully pinged 99.206.102.3 Successfully pinged 99.206.102.14 Successfully pinged 99.206.102.17

 
 

well, that worked out.  while the cmd shell has an IF statement, it doesn’t have a true if/then/else conditional statement.  you can simulate this in batch script… but you can’t do it with the cmd shell.  anyway, here’s the equivalent in powershell.  note though, that we can use if/then/else and can output results if the ping fails.  :)

for ($i = 1; $i -le 255; $i ++) {If ((Get-WmiObject win32_pingstatus -Filter "address='99.206.102.$i'").Statuscode -ne 0) {"Failed to ping 99.206.102.$i"} else {"Successfully pinged 99.206.102.$i"}}

Successfully pinged 99.206.102.1
Successfully pinged 99.206.102.2
Successfully pinged 99.206.102.3
Failed to ping 99.206.102.4
 
 
the first method was using the wmi class win32_pingstatus.  for the hell of it, here’s the same thing, using the .net ping method.  notice we have to initialize the ping object first, though.

$ping = New-Object System.Net.NetworkInformation.Ping

for ($i = 1; $i -le 255; $i ++) {If ($ping.Send("99.206.102.$i").Status -ne "Success") {"Failed to ping 99.206.102.$i"} else {"Successfully pinged 99.206.102.$i"}} Failed to ping 99.206.102.1 Failed to ping 99.206.102.2 Successfully pinged 99.206.102.3 Failed to ping 99.206.102.4

 
 
the for statements look pretty identical.  so, first cmd shell, then powershell:
for /l %<variable> in (<start>,<step>,<end>) DO <command_block>
 
for (<init>; <condition>; <repeat>) {<command_block>}

Oct 2, 2008

executing batch files remotely with psexec …

if you’ve got a batch file of some sort (bat or cmd) sitting out somewhere that you want to execute remotely, you’ll want to make sure you’re following the right syntax to get this to work.

here are some examples that DO NOT work:

psexec \\myDesktop \\myServer\myShare\test.cmd

 

PsExec could not start \\myServer\myShare\test.cmd on myDesktop:
Access is denied.

 

by default, psexec runs the context in localsystem.  since the system most likely doesn’t have access to the share, let’s give psexec some credentials which has access to the share:

psexec \\myDesktop -u myUser -p myPassword \\myServer\myShare\test.cmd

 

PsExec could not start \\myServer\myShare\test.cmd on myDesktop:
Access is denied.

 

ah, this isn’t going to work either, but we’re getting closer.  the access denied message throws me off a little since i know the password is right.  it seems the problem is that psexec will not execute the .cmd or .bat file without knowing the context in which to execute… so we give it one.  cmd.exe.

psexec \\myDesktop -u myUser -p myPassword cmd /c \\myServer\myShare\test.cmd

 

C:\WINDOWS\system32>mkdir c:\testme
cmd exited on myDesktop with error code 0.

 

now there we go… :)