Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

  • Days Won


Kaido1000 last won the day on November 14 2011

Kaido1000 had the most liked content!

Community Reputation

1 Neutral

About Kaido1000

  • Rank

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
  1. The link was broken. Now it should work
  2. Here is the code that you need: http://depsharee.blo...membership.html
  3. I created White Paper for Configuration Manager administrators who are not so familiar with BITS, WebDAV and Request Filtering.In this document you can read how to configure WebDAV, Request Filtering, how to configure WebDAV and Request Filtering with APPCMD and PowerShell and how to troubleshoot software distribution issues and etc. Zip file includes PowerShell exaxmples as well Best, Kaido Jarvemets Configuration Manager MVP http://depsharee.blo...-filtering.html IIS_WebDAV_BITS_ja_Request_Filtering_04_11_11_document_with_script1.zip
  4. The main factors that contribute to job backlogs include the following: The distribution of large software packages. An SMS hierarchy that includes offline sites. See http://support.microsoft.com/kb/836553 We followed these steps to delete the sending jobs and try to recover the backlog: 1. Stop the SMS Executive and Site Component Manager services on the site server. 2. Run the following command from this folder: <ConfigMgr installation directory>\bin\i386\00000409 Preinst.exe /deljob <Site Code> Run this command once for all site codes for sites attached to the site where we have the backlog. Run it also for the parent site. 3. Delete the .srq and .srs files from the following folders: Sms_root_folder\Inboxes\Schedule.box\Requests -and- Sms_root_folder\Inboxes\Schedule.box\Outboxes\Lan 4. Delete the files from "tosend" and "LAN" folders in schedule.box which are more than 6 hours old. As the replication manager would tend to create compressed package files for the jobs which are more than 6 hours old. 5. Start the SMS Executive and Site Component Manager services on the site server. 6. Now please check site status – component status Verify there are no errors logged for LAN_sender and Scheduler components. 7. Check distmgr.log for any failures on the affected site.
  5. Here is PowerShell based installation: http://configmgrpsh.codeplex.com/
  6. Project Description InstallSiteServer.ps1 is a PowerShell script that installs Configuration Manager 2007 Secondary Site server automatically. Currently this script is written for only Windows Server 2008 R2 and Configuration Manager 2007. InstallSiteServer.ps1 uses XML file based configuration file to read how to prepare site server. The main goal for this project is to simplify as much as possible ConfigMgr Site System installation. You can configure in the configuration file: What server roles will be installed or not What additional software you want to install on that server e.g. WSUS, DOTNET 4.0 etc. Configuration Manager installation files location What hotfixes will be installed What IIS file types should be enabled or not Enable IIS hidden segment removal Send an email with logs to your email This script is divided into four phases and after every phase it will restart the server. Script phases: First Phase Enable Auto Logon Install server roles Configure WebDav Configure IIS File Extensions Configure IIS Hidden Segments Restart Server Second Phase Install additional Software Restart Server Third Phase Install Configuration Manager Restart Server Fourth Phase Install R3 and other Hotfixes Restart Server You can find more information from here : http://configmgrpsh.codeplex.com/ *********************** Author: Kaido Jarvemets Configuration Manager MVP, MCITP, MCTS Blog: Depsharee.blogspot.com
  • Create New...