Where is the IIS log files located?

Where are my IIS log files stored?

To determine where your IIS log files are stored, please perform the following steps on your server:

1. Go to Start, click on Control Panel, then Administrative Tools
2. Run Internet Information Services (IIS).
3. Find your Web site under the tree on the left.
4. Right-click on it and choose Properties.
5. On the Web site tab, you will see an option near the bottom that says "Active Log Format." Click on the Properties button.
6. At the bottom of the General Properties tab, you will see a box that contains the log file directory and the log file name. The full log path is comprised of the log file directory plus the first part of the log file name.

For example, if the dialog box displayed the following values:

• Log file directory: C:\Windows\System32\LogFiles
• Log file name: W3SVC1\exyymmdd.log

SCCM 2012 SP1: How to capture Windows XP SP3 Image

Windows XP Sysprep ready for SCCM OSD Capture Guide

This guide will show you what you need to do to capture a Windows XP Service Pack 3 image, which you can then capture and deploy using Configuration Manager.

First of all, you need to create a full  image that is ready to be captured. This is usually best to install on a virtual machine using VMWare or Hyper-V, however, you can if you want, use a physical machine.

Once you have fully completed your image and have all programs and settings on it that you want, you can start the Sysprep and capture configuration process.

You will need the sysprep files, extra driver files and also the custom sysprep file to complete this process successfully. I have already created these for you and they are available to download from below - note that this is for XP Service Pack 3 - if you are using a different service pack for some reason, either upgrade or get the version of Sysprep for that Service Pack:

Download Sysprep Pack

Once you have downloaded this pack, you can extract the zip files and copy the "DRIVERS" and "SYSPREP" folders to the root of your capture machines C:\ drive.

You should then edit the C:\SYSPREP\sysprep.ini file with your own custom settings, like Company Name, AdminPassword and ProductKey.

THIS IS A CRITICAL PART OF THE PROCESS!!!

If you do not complete this part, if will not work correctly and will limit the image to the hardware that you have built the capture machine on.

Go into Computer Management and then into the Device Manager.

Then Expand the IDE ATA/ATAPI Controllers like below:

You need to ensure that all your hard drive controllers are set to Standard, as you can see from above, mine is currently not so will need changing.

If yours needs changing too, follow the below process, if not, you can ignore the following part;

Double click the controller you need to change then click the "Driver" tab:

Click the Update Driver button, then, when the dialog box appears choose "No not at this time" and click next:

Then click "Install from a list or specify location (Advanced)" and then click next:

Then click "Don't search, I will choose the driver to install":

You should then have the option to select the "Standard" driver that you require, highlight this and click next:

This will then install and complete as below:

Ensure that you do this for all your IDE controllers and it should look similar to below:

Before rebooting the capture machine, you also need to follow the same process to change your "Computer" driver. As below, my default "Computer" driver is "ACPI Uniprocessor PC"

But it should be "Advanced Configuration and Power Interface (ACPI) PC", so follow the above steps to change this so it then should look like the below:

You should then reboot the machine to enable all these settings.

Once rebooted, the machine should then be ready to run the Configuration Manager capture media and the captured image will then run on any hardware.

How can I capture an image using capture media in ConfigMgr 2012

You may want to capture an image of a manually installed computer and Configuration Manager 2012 provides a method of doing just that called Capture Media. This media is created as an ISO file which you burn directly to cd/DVD or mount in a virtual machine and use. But first you need to make sure that the image you want to capture is in the right state, listed below

• workgroup joined

 In order for the image to be captured the computer must be a member of a Workgroup, In other words, the machine you want to capture the image from must not be joined to a domain, if it is then remove it from the domain (join a workgroup).


Step 1. Join a Workgroup

Perform the following on the computer which you want to capture an image of as a local administrator.

Click on Start, Right click on Computer, choose properties, click on change settings to the right of the Computername



click on Change



type in the name of a workgroup to join and click ok



click ok to accept the computer name domain change



you'll be welcomed to the windows-noob workgroup, click ok



and you'll be told to restart, so restart..click ok to restart




Step 2. Create the Capture Media

Perform the following on the Configuration Manager server as a SMSadmin.

Open the ConfigMgr console, click on Software Library, Operating Systems, expand Task Sequences. In the ribbon click on Create Task Sequence Media



when the Create Task Sequence Media wizard appears click on Capture Media



click next and browse to the path of where you want to store the ISO file, give it a name like capture_media.iso



click next, then click on browse beside boot image



select your X86 boot image



click ok, then click on Browse beside Distribution Point



select your distribution point



now your selected boot image and distribution point are listed, click next to continue through the wizard



if you get a UAC prompt accept it



finally the media is done !



if you need to troubleshoot it's creation look at the CreateTSMedia.log file in your confmgr LOGS dir. (D:\Program Files\Microsoft Configuration Manager\AdminConsole\AdminUILog)




Step 3. While in Windows, start the ISO/CD/DVD on the Workgroup Computer

Perform the following on the computer which you want to capture an image of as a local administrator.

if you are using virtual hardware (hyperv or vmware) just mount the ISO on your workgroup computer (click on Media, Insert Disc, browse to the ISO location), otherwise burn the ISO to cd/dvd and insert that burned cd/dvd into the computer you need to capture.

While still in Windows (do not try to boot from this ISO/CD/DVD) you should see the following



click on Run TSMBAutorun.exe

Welcome to the Image Capture Wizard appears, click next..



Enter a path and name for the WIM file, I chose \\sccm\sources\os\captures\captured.wim and then enter the credentials of a user with permissions to write to that location



enter some Image Information



review the summary



and click finish to start the capture process, notice how it prepares the config manager client



and then it syspreps



before rebooting into Windows PE to capture the system



and the capture begins !



success !



all done, the image is captured.



Troubleshooting Tips:

If you see an error in SMSTS.log (probably in C:\Windows\CCM\Logs or C:\Windows\SysWow64\CCM\logs) which sates Waiting for CCMExec service to be fully available, locate the SMS Agent Host service in services.msc and start the service. 

Quote

The capture media seems to work fine on Windows 7 installations where Autoplay is enabled and the media can launch TSMBAutorun.exe automatically. However, if you have to launch TSMBAutorun.exe by navigating to the SMS\bin\i386 folder (for instance if autoplay isn't working or you extract create/extract to a USB key), then the wizard does not launch. This seems to be because when you use explorer to run TSMBAutorun.exe the current working directory becomes SMS/bin/i386 and TSMBAutorun.exe expects to find TSMBootstrap.exe in <currentworkingdir>\sms\bin\x64 (or x86) - which would resolve, as John as found, to an invalid path of D:\SMS\BIN\i386\SMS\BIN\x64\TSMBootstrap.exe.

On newly built systems using MDT2012, I think the Apply GPO Pack step applies a default Windows 7 SP1 local policy that disables autorun - therefore we encounter the issue trying to use the capture media. Simply running gpedit.msc and cancelling the 'Turn off Autoplay' option in 'Computer Configuration/Administrative Templates/Windows Components/AutoPlay Policies' allows the Capture media wizard to run via autoplay.
If you do leave Autoplay turned off, you can workaround the issue simply by opening a command prompt at the root of the capture media drive and running sms\bin\i386 smbautorun.exe.

CREDITS:  Techy Geeks Home & Windows-noob.com

SCCM 2012: How to Manual SCEP Client Installation

How to do it…

1. Log into your SCCM CAS server and launch your SCCM 2012 management console.
2. Navigate to \Software Library\Overview\Application Management\Packages and right click on the object called Configuration Manager Client Package and select Properties.
3. The Configuration Manager Client Package Properties window should pop up, select that tab titled Data Source and locate the Source Folder field.

4. Make note of the path listed in the Source Folder field then enter this same path into Windows Explorer. Once you’ve done this, you can click Cancel to close the Configuration Manager Client Package Properties window.
5. The contents of the folder should be identical to the screen shot below.

6. The only two files in this directory that we need right now are ep_defaultpolicy.xml and scepinstall.exe.  Copy these to files to a thumb drive or a CD-R.
7. Now login to the PC we’re targeting for a manual SCEP installation and insert the media format you chose in step 6.
8. Open a command prompt with admin privileges and enter the following syntax

SCEPInstall.exe /policy C:\scep\ep_defaultpolicy.xml

In your case, the path for ep_defaultpolicy will be the installation media you’ve selected. Press Enter and the SCEP installer should pop up.

9. Proceed through the wizard, making your selections as you go. Once the wizard has completed, make sure that the SCEP client is able to download its initial set of definitions.

How it works…

The hardest part of this recipe is locating your SCEP client installation media, because the only copy you’ll have is the one that’s been bundled with the SCCM client installation package.
By copying both the SCEP install exe and the policy xml file and then running them manually on a target client, you’ll end up with a SCEP client that starts off with a similar configuration to your normal SCCM-deployed SCEP clients.
Keep in mind that any future changes to this PC’s SCEP policy will need to be done manually. Also, in order to get definition updates, this PC’s SCEP client will either need to be able to reach Microsoft Updates on the internet or a WSUS server in your environment that is enabled to push SCEP definitions.
It goes without saying that any Antivirus related events on this PC will not be reported to the SCCM server. So it will be up to the user of this PC to keep an eye on what’s going on with the system – much like you would manage an AV client on your home computer.

SCCM 2012: Distribution Point is not updating the content after upgrading SCCM 2012 to SP1

Distribution Point is not updating the content after upgrading SCCM 2012 to SP1

Recently I updated our production SCCM 2012 to SP1.  The install seemed to go fine and a few tests passed when I was on the primary server. I tried to open the Admin Console installed found it wouldn't connect to the site.  After running the console installation again, it worked. Just deploy the console to a collection to all who have it installed?  I tried to do so, but it never deployed.

Here's why - My primary DP (only local one) isn't updating content.  My other 3 remote ones are.  I checked the logs and here's what I found

Console / Monitoring Console / Monitoring

Distribution Manager failed to find or create the defined share or volume on distribution 

Distribution Manager failed to process package SCCM Console SP1

I checked my distmgr.log file and that is showing like that,

distmgr.log

Failed to set share security on share \\XYZ2.domain.com\SMSSIG$. Error = 5

Failed to set access security on share SMSSIG$ on server XYZ2.domain.com

DPConnection::Disconnect: Revert to self

Cannot find or create the signature share.

STATMSG: ID=2324 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=XYZ2.domain.com SITE=ABC PID=2340 TID=6220 GMTDATE=Tue Jan 09 15:16:35.474 2013 ISTR0="["Display=\\ABC2.domain.com\"]MSWNET:["SMS_SITE=BBS"]\\XYZ2.domainy.com\" ISTR1="XYZ001A1" ISTR2="SMSSIG$" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="XYZ001A1" AID1=404 AVAL1="["Display=\\XYZ2.domain.com\"]MSWNET:["SMS_SITE=ABC"]\\XYZ2.domain.com\"

Error occurred. Performing error cleanup prior to returning.

So far, I opened the SMSSIG$ & SMSPKGE$ shares on the server and compared NTFS & Share permissions to other DPs which looked good.  I also added the host mane of the primary site server as well as the sccm service account with full rights to them, but it didn't help any.

 

Solution:

I had my Site System Installation Account set to my service account which I use for most everything.  

We changed that back to "Use the site server's computer account to install the site system."

After doing that, I restarted the SMS_Executive services updated my packages, and they worked!

SCCM 2012 How to Enable Software Inventory

How To: Enable Software Inventory in SCCM 2012

In order to collect data for hardware and software reports in Asset Intelligence, you must enable the Hardware inventory Agent in the Client Settings Policy (Administration – Client Settings – Default Client Settings / Or whatever Policy you want to use).
Further you will have to enable the required Classes for the Inventory.
To do this:

1. Go to “Assets and Compliance“
2. Right click the “Asset intelligence” Folder
3. Click “Edit Inventory Classes”
   
4. Check the required Classes (see list below) or enable all Classes
   
5. Click OK
6. Wait for the next Policy refresh and Hardware Inventor Cycle of your client computers as you defined in the Client Policies

The following Classes are required for Hard- and Software inventory reports:

• SMS_SystemConsoleUsage
• SMS_SystemConsoleUser
• SMS_InstalledSoftware
• SMS_AutoStartSoftware
• SMS_BrowserHelperObject
• SoftwareLicensingService
• SoftwareLicensingProduct
• Win32_USBDevice

SCCM 2012 Inventoried Software Empty

SCCM 2012 Inventoried Software Empty: Quick Tip!

A frequent question with System Center Configuration Manager is “where are my inventoried software items”?  In many of these cases people are seeing the software detected and visible through resource explorer, but the software isn’t showing up in “Software Items”.   In this case you can see populated data in the software items area:

The solution is actually quite simple.  In Asset Intelligence you need to select the appropriate classes for detection, especially including the “SMS_SoftwareInstalled” class. 

You can learn more about the class here:
http://msdn.microsoft.com/en-us/library/cc144824.aspx

Also, here is a screenshot of the configuration for Asset Intelligence:


You’ll note that this is very important in System Center Service Manager as well, as the detected software items are synchronized to Service Manager’s CMDB and relationships are made to the computer CIs.

"The User Profile Service failed the logon” error message

Today when I log on to my lap, I certainly got this error message. "The User Profile Service failed the logon” error message

Solution:

Click Start, type regedit in the Search box, and then press ENTER.

In Registry Editor, locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

In the navigation pane, locate the folder that begins with S-1-5 (SID key) followed by a long number.

Click each S-1-5 folder, locate the ProfileImagePath entry in the details pane, and then double-click to make sure that this is the user account profile that has the error.

Collapse this imageExpand this image

1. If you have two folders starting with S-1-5 followed by some long numbers and one of them ended with .bak, you have to rename the .bak folder. To do this, follow these steps:
   1. Right-click the folder without .bak, and then click Rename. Type .ba, and then press ENTER.
      
      Collapse this imageExpand this image

      
   2. Right-click the folder that is named .bak, and then click Rename. Remove .bak at the end of the folder name, and then press ENTER.
      
      Collapse this imageExpand this image

      
   3. Right-click the folder that is named .ba, and then click Rename. Change the .ba to .bak at the end of the folder name, and then press ENTER.
      
      Collapse this imageExpand this image

      
2. If you have only one folder starting with S-1-5 that is followed by long numbers and ends with .bak. Right-click the folder, and then click Rename. Remove .bak at the end of the folder name, and then press ENTER.

• If you have two folders starting with S-1-5 followed by some long numbers and one of them ended with .bak, you have to rename the .bak folder. To do this, follow these steps:
  1. Right-click the folder without .bak, and then click Rename. Type .ba, and then press ENTER.
     
     Collapse this imageExpand this image

     
  2. Right-click the folder that is named .bak, and then click Rename. Remove .bak at the end of the folder name, and then press ENTER.
     
     Collapse this imageExpand this image

     
  3. Right-click the folder that is named .ba, and then click Rename. Change the .ba to .bak at the end of the folder name, and then press ENTER.
     
     Collapse this imageExpand this image

     
• If you have only one folder starting with S-1-5 that is followed by long numbers and ends with .bak. Right-click the folder, and then click Rename. Remove .bak at the end of the folder name, and then press ENTER.

Double-click the folder without .bak in the details pane, double-click RefCount, type 0, and then click OK.

Collapse this imageExpand this image

Click the folder without .bak, in the details pane, double-click State, type 0, and then click OK.

Collapse this imageExpand this image

Close Registry Editor.

Restart the computer.

Log on again with your account.