Replies

Hi,

I think the “Realm” setting only applies to Basic and Digest Authentication in IIS, not Integrated Windows Authentication – hold on, I’ll check. Yes, it does. The “Realm” field only becomes available when either of these two methods of authentication are selected. I’m sure there is a solution to this and I think its setting the SPN, but I want to be sure?

Thanks for your reply,

Thanks for your reply – I thought this was the case.

Ade

Thank you – that worked beautifully!

Much appreicated,

Yep, its given me a solution…have added these two lines in the logon script:

reg delete “HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerMenuOrder” /f
reg add “HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerMenuOrder” /f

Tested OK, now rolling out across the domain!

Many thanks for the quick response.

Cheers,

Thanks for the replies – I thought so!

Will check out the link for add-in, but will probably put some bold, red text on the first slide!

Cheers,

Quick update and closure of this thread…

Have given up trying to script the System Restore and reboot/shutdown together. Have opted for manual reboot by user, or remote client, after System Restore has been set. Am assuming that it’s our hardware that is not responding properly to the reboot/shutdown script.

Therefore, we have ended up with two scripts. One to enumerate the System Restore Points available and the other to perform the actual System Restore (both are below). We needed these to run against remote PC’s that were in safe mode. To do this, we had to enable the “Allow Remote Administration” exception in the Windows XP SP2 non-domain settings firewall (risky, but had to be done). We did this via Group Policy.

Here are the two scripts…

Long code fragment (over 3,000 characters) moved to attachment by HansV

Thanks to those of you who responded on this thread.

Cheers,

Thanks for that Charlotte.

It does look like a hardware issue (related to the force reboot code). We have progressed a little further now…

If we just run the System Restore code against the remote machine (whilst at Ctrl Alt Delete screen), and then get the user to re-boot the local PC via the shutdown button on the logon screen; the machine shuts down and the “Performing System Restore” gui appears. The System Restore completes OK, the machine reboots and the a successful System Restore event is logged.

So, it does look like a hardware issue with the force reboot code, doesn’t it? At least we’re partly automating the process…

All I have to do now is get the System Restore code to run against the machine when it is booted to “Safe Mode with Networking” (not working at present). This is our driver for this script – we have a hardware issue where we can only boot some PC’s to Safe Mode with Networking; performing a System Restore gets them going again…and we need to be able to do it over our WAN.

I assume the System Restore script is not working in Safe Mode as the WMI classes may not be loaded?

Any pointers out there please?

Cheers,

Hi Gary,

Thanks for that. You’re right…I was assuming that the location of normal.dot, within the Users Templates location, made it more user specific. Perhaps, as you say, it doesn’t. Having done some searching around the Lounge, I think I will be adding some VBA to our global template that will change the default font of the users normal.dot programmatically (see post 423877). NB: I have used the Office 2003 CIW to specify a standard, network, location for Workgroup and Startup templates in Word.

This way, I can be sure that the VBA will run whenever a user (exisiting or new) opens Word 2003, rather than having to wait for all my users to use Word, create their own normal.dot and then pull a new one from the network – also avoids having to add an error trap to the network script that would copy a network normal.dot over a users normal.dot (should it not exist).

Again, having looked around the Lounge (particularly in the VB/VBA forum) there seems to be lots of IT Managers looking for a solution to this problem – what strikes me as bizzare is that there is nothing on the Microsoft KB or Office site to tackle this issue?

Many thanks,

Hi and thanks for your reply,

Your suggestion is what I would normally (forgive the pun) do for an Office/Word 97 installation, but in Office/Word 2003 the normal.dot is much more user specific and, I assume, more critical to the correct functioning of the newer features in Word 2003 (certificates, macro security etc).

I assume, again, that this is why Microsoft instruct you not, under any circumstances, to open any Office 2003 program on the PC to be imaged; as doing so adds specific user configuration info to the registry and other places (including the creation of normal.dot for the user). Consequently, I need to manipulate the normal.dot after image deployment and after a user has logged in (and their normal.dot created) – as you say, I could do this via scripting from the network…I’m just a bit nervous about the corruption that might be caused to Word 2003 configuration?

Can anyone else shed some light on this, may be some specific experience of Word 2003?

TIA,

Many thanks for the pointer – on my way there now!

Regards,

Ah, got you. Thanks. Have decided to use WMI and have produced the following script:

strComputer = “.”
strTarget = “192.168.0.1”

Set objWMIService = GetObject(“winmgmts:” & “{impersonationLevel=impersonate}!” & strComputer & “rootcimv2”)
Set colPings = objWMIService.ExecQuery (“Select * From Win32_PingStatus where Address = ‘” & strTarget & “‘”)

For Each objPing in colPings
If objPing.StatusCode = 0 Then
MsgBox “Ping Received From:” & vbtab & strTarget & vbcrlf & _
“Responding Address:” & vbtab & objPing.ProtocolAddress & vbcrlf & _
“Bytes Sent:” & vbtab & vbtab & objPing.BufferSize & vbcrlf & _
“Time:” & vbtab & vbtab & vbtab & objPing.ResponseTime & ” ms” & vbcrlf & _
“TTL:” & vbtab & vbtab & vbtab & objPing.ResponseTimeToLive & ” seconds”, 64, “Title text”
Else
MsgBox strTarget & ” did not respond to ping.”, 16, “Title text”
End If
Next

Set strComputer = Nothing
Set strTarget = Nothing
Set objWMIService = Nothing
Set colPings = Nothing

Many thanks to everyone for all the pointers on this.

Cheers,

Ah, got you. Thanks. Have decided to use WMI and have produced the following script:

strComputer = “.”
strTarget = “192.168.0.1”

Set objWMIService = GetObject(“winmgmts:” & “{impersonationLevel=impersonate}!” & strComputer & “rootcimv2”)
Set colPings = objWMIService.ExecQuery (“Select * From Win32_PingStatus where Address = ‘” & strTarget & “‘”)

For Each objPing in colPings
If objPing.StatusCode = 0 Then
MsgBox “Ping Received From:” & vbtab & strTarget & vbcrlf & _
“Responding Address:” & vbtab & objPing.ProtocolAddress & vbcrlf & _
“Bytes Sent:” & vbtab & vbtab & objPing.BufferSize & vbcrlf & _
“Time:” & vbtab & vbtab & vbtab & objPing.ResponseTime & ” ms” & vbcrlf & _
“TTL:” & vbtab & vbtab & vbtab & objPing.ResponseTimeToLive & ” seconds”, 64, “Title text”
Else
MsgBox strTarget & ” did not respond to ping.”, 16, “Title text”
End If
Next

Set strComputer = Nothing
Set strTarget = Nothing
Set objWMIService = Nothing
Set colPings = Nothing

Many thanks to everyone for all the pointers on this.

Cheers,

Many thanks – have had a quick look around and it seems to be a major point of discussion!

I have attempted to create a script that will use WshShell.Run to open a command window, run ping and return the output to a string. My theory is that I can specify 0 as the value for the window, which makes the command window hidden. Its a bit messy and its not working at the moment, can anyone see where I’m going wrong?

Dim pingip
Set WshShell = Wscript.CreateObject(“Wscript.Shell”)
pingip = WshShell.Run (“cmd /K & ping 192.168.0.1”), 0, False.StdOut.ReadAll
MsgBox pingip
Set WshShell = Nothing
Set pingip = Nothing

Cheers,

Many thanks to both of you for that – the one liner does the job required and the WMI method provides some more functionality . Anyway of hiding the command window that appears when using the Exec method of WScript.Shell?

Cheers,

Many thanks to both of you for that – the one liner does the job required and the WMI method provides some more functionality . Anyway of hiding the command window that appears when using the Exec method of WScript.Shell?

Cheers,