Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

  • Days Won


slater7607 last won the day on January 30 2012

slater7607 had the most liked content!

Community Reputation

2 Neutral

About slater7607

  • Rank
  1. I've been able to get Office 2010 deployed through using the OCT but I was wondering if anyone has any idea on how to enable the Excel add-ins via the installer or post-install. The add-ins I'm talking about are the Analysis ToolPak and Solver Add-ins through Options-->Add-ins I haven't been able to find anything on this so I was just wanting to check if anyone else had any experience with it.
  2. I'm just curious, I find it a lot easier for the HTML portions to use Dreamweaver to handle the layout in design view but HTAedit and Notepad++ handle the coding portions very well. Just a preference I guess
  3. I'm still new to the whole HTA game but I've figured out my way around how they work and am really pleased with how powerful they can be. I struggled at first with getting everything going, I have moderate web design experience with Dreamweaver and I was able to figure out how to edit the doctypes for that to allow editing in design view, but bounce back and forth between HTAedit and Notepad++ to edit code. Anyone else use any good tools for writing and editing HTAs?
  4. Thanks for the info, I made a small function with some ideas I got from here: https://blogs.technet.com/b/deploymentguys/archive/2010/04/26/exporting-all-sccm-variables-to-a-log-file-for-debugging.aspx?Redirected=true I'm using the _SMSTSLogPath to determine where the TS is writing smsts.log to, do you happen to know if it will take any logs in that folder back to the CCM\Logs folder after everything is done?
  5. I'm working on an HTA frontend for our task sequences, starting with a basic computer information one. I had previously used a .vbs that did a wscript.echo command that wrote a line in the log file. However, wscript commands inside of an HTA aren't allowed (https://blogs.technet.com/b/heyscriptingguy/archive/2005/10/31/how-can-i-start-an-application-from-an-hta.aspx?Redirected=true) Is there any other way to pass a line into the smsts.log file from the HTA?
  6. Just as a follow up, I believe we have the problem fixed and it's pretty uncommon since it was something specific to our environment. After backing up logs and pouring through them I found nothing that indicated any problems with the servers, just notifications of the outbox folder for hinv.box had X amount of files in it but they would never process from the MP to the site server. We are using Symantec Endpoint Protection as our firewall/anti-virus program in our organization and we had previously found a bug in somewhat older versions (11.0.5 and 11.0.6) that affected Samba processes on server shares. It was intermittently causing file transfers to halt and would not cancel or terminate the connection until either the server or the client machine was rebooted. After upgrading the SEP 12.1 which we were currently testing for rollout the problems have not occurred for the past 8 days. Hopefully this continues to be the case but in the remote chance someone else comes across this and applies to them hopefully this puts them on the right track.
  7. I had a request from a previous post to share how we are changing the computer description during OSD. We currently use this to have our techs enter in the location of the computer to help with automating our inventory. Also, if anyone has a better way of doing this please feel free to contribute. Also, in our environment the description does not filter back to AD it only remains local to the machine but YMMV as I haven't looked too far into that. The description still filters back in through a custom report so it achieves everything that we need it to. 1. Create a computer description TS variable 2. Include the following script as part of one your packages and execute it sometime before your OS install (we include all of our scripts in the MDT Toolkit package) TSComputerDescPrompt.vbs Dim oTaskSequence, strComputerDesc Set oTaskSequence = CreateObject ("Microsoft.SMS.TSEnvironment") ' The wscript.echo commands are logged in SMSTS.log for troubleshooting. ' They are not displayed to the end user. sComputerDesc = InputBox ("Enter desired computer description." &VbCrLf & VbCrLf & "X Domain - Computer location example: BUILDING ROOM #" &VbCrLf &VbCrLf & "Domain - Tag Number example: 10-0454 or 106183","Computer Description",,,30) oTaskSequence("OSDComputerDesc") = sComputerDesc wscript.echo "Set Task Sequence variable OSDComputerDesc to: " & strComputerDesc 3. Execute this final script with another task sometime after the OS install, we do it right after. TSComputerDesc.vbs Dim objShell Dim oTaskSequence, strComputerDesc Set objShell = WScript.CreateObject ("WScript.shell") Set oTaskSequence = CreateObject ("Microsoft.SMS.TSEnvironment") ' The wscript.echo commands are logged in SMSTS.log for troubleshooting. ' They are not displayed to the end user. strComputerDesc = oTaskSequence("OSDComputerDesc") objShell.run "reg add HKLM\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters /v srvcomment /d " & strComputerDesc & " /f" wscript.echo "Computer Description changed to: " & strComputerDesc
  8. Thanks for the info, I do not see any applicable error messages under the system status so far but I will be checking it periodically. Also, the mp_hinv.log is too busy and a new log gets created just about every other hour so I'm going to put in a script to backup the logs hourly this week and go through them once the problem occurs. I'll let you know if I find anything suspicious, thanks!
  9. Does this happen for every report that you are trying to run, or is it only on some that would return a large number of records? We had an issue that was very annoying and not very easy to track down the problem. Try running a report that would only return < 100 or so records and see if it works.
  10. I followed a similar approach but took it a step further. We found that the task sequence would fail to join machines to our domain due to invalid characters or computer names that were too long. I threw in some error checking from some other scripts I found online and made a few tweaks. It will pre-populate the field if it has a known computer name and also does some logging smsts.log I also have one for filling in the computer description which we use for inventory if anyone else is interested in that. Dim objRegEx Dim Matches, Match Dim strPattern, sNewComputerName, strReason Dim boolLength, boolValid Dim oTaskSequence, sTSOldName Set oTaskSequence = CreateObject ("Microsoft.SMS.TSEnvironment") Set objRegEx = New RegExp ' Define valid patterns as a character not in (a-z, A-Z, 0-9, or -) strPattern = "[^a-zA-Z0-9-]" ' Get old computer name, or random name if unknown sTSOldName = oTaskSequence("_SMSTSMachineName") ' The wscript.echo commands are logged in SMSTS.log for troubleshooting. ' They are not displayed to the end user. Do strReason = "" sNewComputerName = InputBox ("Enter desired computer name." & VbCrLf & VbCrLf & "Computer names must be 3-14 characters, and include a-z, A-Z, 0-9, -, and _ ONLY.","Computer Name",sTSOldName,,30) ' Check length - must be less than 16 charatcers If Len(sNewComputerName) <= 15 Then boolLength = True Else strReason = strReason & "Computer name too long. Please choose a name from 1-15 characters in length." & VbCrLf boolLength = False End If ' Check character validity boolValid = True ' Return all matches for invalid characters objRegEx.Global = True objRegEx.Pattern = strPattern ' Generate collection of matches Set Matches = objRegEx.Execute(sNewComputerName) ' Check for matches on invalid characters For Each Match In Matches strReason = strReason & "Invalid character """ & Match.Value & """ found. Please use only a-z, A-Z, 0-9, and -." & VbCrLf boolValid = False Next If Not (boolLength And boolValid) Then MsgBox "Invalid name """ & sNewComputerName & """ entered!" & VbCrLf & VbCrLf & strReason,vbCritical+vbOKOnly+vbSystemModal,"Invalid Name Entered" Loop While Not (boolLength And boolValid) oTaskSequence("OSDComputerName") = sNewComputerName wscript.echo "Set Task Sequence variable OSDComputerName to: " & sNewComputerName
  11. This problem is still occurring about ever 3-5 days. Still hoping someone has any insight on the problem. Thanks!
  12. Hello, We have recently implemented SCCM 2007 in the past 6 months and just about every week we have problems with our hardware inventory processing back to the site server. The SMS\MP\OUTBOXES\hinv.box folder will begin to fill up with .MIF files and stay there until we rebooot our MP and site server. At that time all of the data will process for a couple of hours depending on how much inventory is backlogged. This isn't ideal for a few reasons because 1.) we don't have any idea why/when it happens 2.) rebooting servers midday and then consuming all of the server resources for a few hours hinders our ability to use the server. Has anyone else come across this problem and/or found a permanent solution? I'm not sure where to look logwise and any help would be appreciated. Here is what the hinv.box folder looks like. About 90% of the files are current hardware inventory .MIFs that are created within the previous 3 or 4 days (we have hardware inventory scheduled on a 5 day cycle) and the only outboxes that fill up are for hardware inventory.
  • Create New...