Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

My Information

  • Agent Count

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm getting a similar error with the same configuration as above, windows 8.1. IE is default browser. The issue for me is probably something to do with the fact that we have ScreenConnect's IIS component installed as a sub-site under our Labtech server in the mode where it shares the SSL certificate, so the path required currently is : https://labtech.foobar.com/RemoteSupport/LaunchHostClient.ashx?ID=BgIAAACkAABSU0ExAAgAAAEAAQDpYbB3cqDG This results in the following ASP error: Sequence contains no matching element Sequence contains no matching element Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.InvalidOperationException: Sequence contains no matching element Source Error: The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL: 1. Add a "Debug=true" directive at the top of the file that generated the error. Example: <%@ Page Language="C#" Debug="true" %> or: 2) Add the following section to the configuration file of your application: Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode. Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario. Stack Trace: [invalidOperationException: Sequence contains no matching element] System.Linq.Enumerable.First(IEnumerable`1 source, Func`2 predicate) +2615110 LaunchHostClient.ProcessRequest(HttpContext context) +274 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +341 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +69 Hopefully that's enough info without enabling the debug code. Is this down to the IIS configuration?
  2. So after enabling Microsoft Update and manually pushing patches from LT, the error message changed: ---- Installing: Windows 7 Service Pack 1 (KB976932) Result: Windows Update Version 7.4.7600.226 Windows 7 Service Pack 1 (KB976932) could not be downloaded, but will be reattempted. ---- Not sure if we're looking at the same issue or not, but I'll try the update agent patch script posted in the Script Exchange and see. It is definitely something particular to the machine, the rest of the site has no issues. ETA: And all the other Win7 machines at the site are still on the .226 agent as well.
  3. Out of curiosity, is Microsoft Update enabled on those systems? It is on most of mine in the fleet and I'm not seeing this issue a lot. I located one problem system that I'm working with. The majority of mine are patching just fine. This one was showing the following symptoms: - Patching screen showed: Result: Windows Update Version 7.4.7600.226 Error Occurred Durring Install: Exception from HRESULT: 0x8024001E - Opening Windows Update manually showed a green check, updates for Windows Update only, no updates needed - When manually running Check for Updates, prompted to install the latest update client - Ran 'Enable Microsoft Update' script - After enabling Microsoft Update, the Windows Update control panel did show a Red status and Updates Needed - System is also missing Windows 7 SP1 I'm pushing patches manually now to see if this resolved this situation.
  4. Now I started digging into this a bit more. The latest MS article regarding the update agent from August states: http://support.microsoft.com/kb/949104 I suspect the installable version of the update client for Win7 that was release was done so only to resolve issues. It does not seem to be generally necessary, at least in my fleet. So far yes, in general am seeing the appropriate versions aside from a few Win8 systems that have not been updated to 8.1. The Windows 7 clients are generally all on the 2012 .256 version and working fine. I don't see a widespread update problem with 2012 servers, but I'm going to check some versions there too.
  5. I spot checked a bunch of my systems and I don't seem to be having this issue across my client base - however, I had previously added an 'Enable Microsoft Update' script to my Onboarding and Maintenance scripts, and I am also now wondering if this handled the Update client.
  6. If you happen to have bought App-Care, and grub around the scripts there, there's a great notification script in there that uses a small EXE. I really wish it was pulled out and made available to the rest of LT as a standalone feature. Look in, for instance, the !Daytime Update script for the lines referring to AppNotify.exe. I've tinkered with it a bit to try and adapt it but never have completely pulled out the notification bits and wrapped them around the standard Contract maintenance scripts.
  7. I've been trying to pursue another method, but haven't been getting very far with it. They now have a windowsclient.exe session launcher that initiates a SC session from the client side. It seems like it should be possible to just launch this client programatially, and there are a few discussion about it: http://forum.screenconnect.com/yaf_postsm17519_Guest-and-Host-autojoin-command-line.aspx http://forum.screenconnect.com/yaf_postst4399_Commandline-switches.aspx It seems like it should be possible to just deploy this generic windowsclient.exe launcher, and then create sessions on demand using Labtech scripting, but I am not getting very far following along in these threads. This would be a great solution though, if it would work - less administrative effort about organizing a bunch of permanently installed clients in my ScreenConnect page if I can just run a script to launch a session on demand.
  8. To answer my own question, checking out 'DB>doc' now from Codeplex, which is also a bit old (1.0 release 2012). https://sqldbdoc.codeplex.com/
  9. HI all; Looking for a lightweight, quick and dirty MS SQL server documentation script. So SYDI-SQL hasn't been updated since about 2005 and gives me various errors when run against some newer SQL editions. I'm not looking for much, just a dump of databases and their sizes, and maybe any configured backup jobs, output as HTML or TXT so it can be displayed in a custom tab. SYDI-SQL was perfect but is evidently broken now. If nobody knows of anything that connects directly to a SQL server I'll just probably write something in powershell that grubs around in directories looking for MDF files, but getting the jobs as well would be a nice plus.
  10. Even better then! That's extremely cool. This is way better than the handful of CMD scripts I was pulling together myself.
  11. Question/request - if we want to edit the tabs and install custom icons for programs that aren't covered, I assume we risk having that blown away when we upgrade. If there was a user config file alongside the default config file so that we could preserve modifications somehow, that would be awesome.
  12. Yes, you do. It is strongly recommended that this be installed on another box from the LTServer, although it technically *can* be done. However once you grow beyond a few hundred clients you'll start running into memory issues.
  13. The base Eset Endpoint antivirus product will do this: One small caveat: This area of the configuration is not handled by the fully-managed Labtech ESET's policy editor. You'll need to manually roll that part of the policy in your ESET Remote Administration Server. However, this is pretty trivial once you get to know the RAS.
  14. In my experience, none of the major general-purpose AV systems catch much. I've worked with Symantec, Trend, ESET and McAfee, and they're all just "okay" when it comes to today's malware. We use ESET at a front-line solution because it is relatively cheap, lightweight, and supported by Labtech. The approach we take is to use Labtech's Hitman Pro solution as a "second opinion" scanner. We use it in two ways - we run a nightly scan for all users, and we also set up a Monitor to run an immediate free scan if ESET throws a "malware found but cannot clean" message. We also implemented the Blacklisted Software monitor to trigger a HMP if any software on the Blacklist is found installed. This combination seems to work well for us.
  • Create New...