Windows script issues to check TFTP status (SCCM PXE check)

Hi,

The SCCM guys have issues with SCCM's TFTP (PXE) functionality on odds days.

I wrote this script that calls the windows tool "tftp.exe" (some code comes from SW's findfile.vbs example)

The script requests a file from the TFTP server, checks if it exists for the downloaded location and then deletes the file.

I'm unable to get it to download the file file when I add the code to the Windows Script monitor........but it works great from the command line in Windows.

My VB is terrible and I'm not sure if I need to tweak something to get it to call the windows command correctly.

I have added the "tftp.exe" app into both C:\temp\tftp and in a windows path location on the Orion server.

Here is the code:

Option Explicit

Const FILE_FOUND = 0, INVALID_PARAMS = 1, FILE_NOT_FOUND = 1

Dim oShell, fileName, fso, monFile

fileName = "\\10.160.8.186\c$\temp\tftp\tftpfile"

Set oShell = WScript.CreateObject ("WScript.Shell")

oShell.run "cmd cd /C C:\temp\tftp & tftp -i 10.160.8.186 get SMSBoot\x86\wdsnbp.com \\10.160.8.186\c$\temp\tftp\tftpfile"

Set fso = Wscript.CreateObject( "Scripting.FileSystemObject" )

' sleep for 5 seconds for file to download

wscript.sleep 5000

If fso.FileExists( filename ) Then

oShell.run "cmd cd /K del \\10.160.8.186\c$\temp\tftp\tftpfile"

WScript.Echo "Message:" & fileName & " :: FOUND - PASS"

WScript.Echo "Statistic: 0"

WScript.Quit( FILE_FOUND )

Else

oShell.run "cmd cd /k del \\10.160.8.186\c$\temp\tftp\tftpfile"

WScript.Echo "Message:" & fileName & " :: NOT FOUND - FAIL"

WScript.Echo "Statistic: 0"

WScript.Quit( FILE_NOT_FOUND )

End If

Any help would be appreciated as I know a few other people would like some sort of TFTP monitor.

Ben

Find more posts tagged with

sam

Accepted answers

aLTeReGo

From your script I can see that you're accessing files on a remote network share. All vbscript is executed in the context of the local system account which has no permissions to access remote network file shares. You'll likely need to use PowerShell which natively allows for impersonation or add your own impersonation method into your vbscript.

All comments

aLTeReGo

ceomservers

Thanks aLTeReGo.

My PowerShell is worse than my vb so I might google on how to do a 'runas' or impersonate a user as you described within the vbscript......

ceomservers

I have tried a new piece of code to just test the ability to download the file using tftp with 'runas' in the vb.....this works from the command line but doesn't work in SAM:

I have removed any account details.

CODE BEGIN:

Option Explicit

Dim oShell, WshShell

set WshShell = CreateObject("WScript.Shell")

Set oShell = WScript.CreateObject ("WScript.Shell")

oShell.run "runas /user:username@domain.network ""tftp -i 10.160.8.186 get SMSBoot\x86\wdsnbp.com c:\temp\tftp\tftpfile.shsccm01"""

WScript.Sleep 1000

WshShell.Sendkeys "password~"

CODE END

Maybe I should pull a powershell for dummies book out

aLTeReGo

This again likely has to do with the limited permissions of the system account that the Job Engine runs under. It could also be running into issues with UAC. One of our Script Gurus may be best suited to help answer your questions.

mrxinu

Is there any reason (aside from not knowing the language) that you're not using PowerShell for this (older version of SAM, maybe)? If not, let me know and I'll re-write it for you and post it here.

Update: Looking around a bit I found a tasty sample that acts as a TFTP client on its own using ActiveXpert's ActiveSocket library. If the only reason you're hitting that remote system is because that's where the TFTP binary lives, this may be a better solution. As long as you're on a current version of SAM I can help you get acquainted with the sample below.

Powershell TFTP Client Sample Source Code

ceomservers

I am currently running SAM 5.0.1 and was only using VB as I was able to find some script examples on the web and combine them until something worked locally. (I have no experience with anything other than basic SQL reporting).

The desktop team have several remote SCCM servers and they have a 'PXE Service Point'. For some odd reason the TFTP / PXE server will stop responding even though WDS is up and happy. Its not often but generally happens when they really need it and I would like to report on it, whilst we try and stop it form happening at all.

My idea was to:

pull a file down from the PXE / TFTP server (SCCM server) - using tftp.exe
check if it exists locally
delete the file
try again in 10 mins

I have been through a lot of the forums here and elsewhere to come up with this idea but there is always better ways of doing things. Even just a positive response that the file exists through a TFTP request would be simpler.

I would appreciate some help with powershell but only if you have time. Thanks also for the link, its above my head but I'm keen to learn!

Thanks, Ben

mrxinu

Hi Ben, I'll give it some thought and get back to you tomorrow afternoon (today is pretty well packed). It's definitely doable with some PowerShell.

mrxinu

Leave it to me to miss the fact that the library costs hundreds of dollars. Let's see what we can do with calling out to the TFTP binary. I've set up a server locally to play with; be right back.