Jump to content


bryanlavalley

Established Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About bryanlavalley

  • Rank
    Newbie

Profile Information

  • Gender
    Male
  1. Seems like a poor may to manage content distribution to enable 'Slow Network' on package(s) when the machine is fast connected. Maybe I'll submit a bug report.
  2. I figured this out yesterday and wanted to share as it may help someone else as the internet failed to help me. Our SCUP 2011 started to fail to launch. It would show the splash screen then crash a few seconds later. In the Application event log there are two entries .NET framework and App Crash error (No help in these errors). Monitoring the size of the SCUPDB.SDF file to grew to ~256MB and that is the max size in the SCUP application (I couldn't figure out how to make this limit bigger.) The SQL Compact Edition 3.5 max size is 4GB. "Fixing it" I used SQL Server Management Stud
  3. I have been trying to determine why our VPN clients are having trouble with downloading content and receiving this error in the CAS.Log 'The number of discovered DPs(including Branch DP and Multicast) is 0'. I have checked the client IP addresses and they are in scope of a boundary. The boundaries are 'fast' connected. The applications are on the DPs and successfully verified (Content validation). Also if a client comes on site the content downloads and installs AOK. The main difference on VPN is that there are two IP addresses. (Local private IP and VPN Address) We added boundarie
  4. Is there a way to change how often logs roll-over or number of backups? Mostly concerned on the client side. Thanks.
  5. I am deploying a Microsoft Hotfix via Software Distribution and it requires a reboot. I can't have workstations reboot during the day and have maintance windows setup to cover that. Maintance Windows: Weekdays: - 12AM to 6AM - 2PM to 12AM All day Sat and Sun I have tested the install and it works nicely once the maintance window is availible; the patch installs and prompts the user to reboot with a timeout set in the 'Computer Client Agent' (240 minutes - 4 hours). This happens around 2PM. Here is my issue: When the patch is deployed to a new collection I start it at 12AM (
×
×
  • Create New...