Content Distribution to Distribution Points -Part I

For storing the content, these are the packages available in Configuration Manager.

1. Software Distribution Packages
2. Application
3. Software Update Packages
4. Boot Images
5. Operating System images and packages

Clients get these packages from distribution point. When content is distributed to the distribution point there are chances that the packages does not reach DP successfully.

From our experience, we have seen this issue happing to many customer and one of our common issues which our customer face.

This flow is on ,how the content distribution happens, Once you know this, you can track where the flow is broken.

Creating a Package

When the package is created from the console then the SMS Provider will write the information to the database. This change is detected by the smsdbmon and the notification file is placed

Note: The highlighted items are the checkpoints to understand the flow so that if broken we can easily find it out

SMSDBMON.log
RCV: INSERT on SMSPackages_G for SMS_Package_ins_upd_SMSProv [P0100017  ][72057594037986121] SMS_DATABASE_NOTIFICATION_MONITOR 11/18/2013 7:10:14 PM 4808 (0x12C8)
RCV: INSERT on SMSPackages_G for SMSPackages_G_Avail_iu [P0100017  ][72057594037986122] SMS_DATABASE_NOTIFICATION_MONITOR 11/18/2013 7:10:14 PM 4808 (0x12C8)
RCV: INSERT on PkgNotification for PkgNotify_Add [P0100017  ][72057594037986123] SMS_DATABASE_NOTIFICATION_MONITOR 11/18/2013 7:10:14 PM 4808 (0x12C8)
RCV: INSERT on PkgNotification for PkgNotify_Add [P0100017  ][72057594037986124] SMS_DATABASE_NOTIFICATION_MONITOR 11/18/2013 7:10:14 PM 4808 (0x12C8)
RCV: INSERT on RBAC_ChangeNotification for Rbac_Sync_ChangeNotification [72057594037928118  ][72057594037986125] SMS_DATABASE_NOTIFICATION_MONITOR 11/18/2013 7:10:14 PM 4808 (0x12C8)
SND: Dropped C:\Program Files\Microsoft Configuration Manager\inboxes\objmgr.box\P0100017.PAN  [72057594037986122] SMS_DATABASE_NOTIFICATION_MONITOR 11/18/2013 7:10:14 PM 4808 (0x12C8)
SND: Dropped C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\P0100017.PKN  [72057594037986123] SMS_DATABASE_NOTIFICATION_MONITOR 11/18/2013 7:10:14 PM 4808 (0x12C8)
SND: Dropped C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\P0100017.PKN  [72057594037986124] SMS_DATABASE_NOTIFICATION_MONITOR 11/18/2013 7:10:14 PM 4808 (0x12C8)
SND: Dropped C:\Program Files\Microsoft Configuration Manager\inboxes\hman.box\72057594037928118.RBC  [72057594037986125] SMS_DATABASE_NOTIFICATION_MONITOR 11/18/2013 7:10:14 PM 4808 (0x12C8)

Once the notification file is received the distmgr will start the processing . It takes the snapshot of the package ,creates a package signature, calculates the hash and also replicates these information to the other sites.

Distmgr.log

Found notification for package 'P0100017' SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:29 PM 3604 (0x0E14)
Used 0 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:29 PM 3604 (0x0E14)
Starting package processing thread, thread ID = 0x1438 (5176) SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:29 PM 3604 (0x0E14)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:29 PM 3604 (0x0E14)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=PRIMARY1.msdindia.com SITE=P01 PID=2656 TID=5176 GMTDATE=Mon Nov 18 13:40:29.912 2013 ISTR0="Notepad++" ISTR1="P0100017" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="P0100017" SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:29 PM 5176 (0x1438)
Start adding package P0100017... SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:29 PM 5176 (0x1438)
The Package Action is 2, the Update Mask is 0 and UpdateMaskEx is 0. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:29 PM 5176 (0x1438)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=P0100017, Version=1, Status=2300 SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:29 PM 5176 (0x1438)
Taking package snapshot for package P0100017 from source C:\Software\Notepad++ SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:29 PM 5176 (0x1438)
Set share security on share \\PRIMARY1.msdindia.com\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:29 PM 5176 (0x1438)
The size of package P0100017, version 1 is 6879 KBytes SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:30 PM 5176 (0x1438)
CreatePackageSignature() called for Package P0100017 with version 1 with source as '\\?\C:\Software\Notepad++'. KeepUnpackedSignature = 1 SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:30 PM 5176 (0x1438)
Successfully created RDC signatures for package P0100017 version 1 SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:30 PM 5176 (0x1438)
Set share security on share \\PRIMARY1.msdindia.com\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:30 PM 5176 (0x1438)
Creating hash for algorithm 32780 SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:30 PM 5176 (0x1438)
The hash for algorithm 32780 is FBAD23A5B5D910EE847C83E53B4BEFB950CBFE8BC0F8F05CDBC6E00518080E2B SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:30 PM 5176 (0x1438)
The RDC signature hash for algorithm 32780 is 2D736B64030C3E5D9B1BF9816D81A00942DE4B7A797B3D7A74998462439219B9 SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:30 PM 5176 (0x1438)
Adding these contents to the package P0100017 version 1. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:30 PM 5176 (0x1438)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=P0100017, Version=1, Status=2376 SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:31 PM 5176 (0x1438)
STATMSG: ID=2376 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=PRIMARY1.msdindia.com SITE=P01 PID=2656 TID=5176 GMTDATE=Mon Nov 18 13:40:31.102 2013 ISTR0="P0100017" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="P0100017" SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:31 PM 5176 (0x1438)
Adding these contents to the package P0100017 version 1. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:31 PM 5176 (0x1438)
Successfully created/updated the package P0100017 SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:31 PM 5176 (0x1438)
STATMSG: ID=2311 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=PRIMARY1.msdindia.com SITE=P01 PID=2656 TID=5176 GMTDATE=Mon Nov 18 13:40:31.601 2013 ISTR0="P0100017" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="P0100017" SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:31 PM 5176 (0x1438)
Created policy provider trigger for ID P0100017 SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:32 PM 5176 (0x1438)
Package P0100017 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:32 PM 5176 (0x1438)
A program for package P0100017 has been added or removed, therefore it needs to be replicated to all child sites. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:32 PM 5176 (0x1438)
Package P0100017 is new or has changed, replicating to all applicable sites. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:32 PM 5176 (0x1438)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=P0100017, Version=1, Status=2301 SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:32 PM 5176 (0x1438)
StoredPkgVersion (1) of package P0100017. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:32 PM 5176 (0x1438)
SourceVersion (1) of package P0100017. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:32 PM 5176 (0x1438)
Adding these contents to the package P0100017 version 1. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:32 PM 5176 (0x1438)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=PRIMARY1.msdindia.com SITE=P01 PID=2656 TID=5176 GMTDATE=Mon Nov 18 13:40:32.986 2013 ISTR0="Notepad++" ISTR1="P0100017" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="P0100017" SMS_DISTRIBUTION_MANAGER 11/18/2013 7:10:32 PM 5176 (0x1438)

Distribute to Local DP

When you add a distribution point to a package the SMS Database Notification Monitor.

SMSDBMON.log

RCV: INSERT on PkgNotification for PkgNotify_Add [P0100017  ][72057594037986132]  SMS_DATABASE_NOTIFICATION_MONITOR  11/18/2013 7:12:04 PM  4808 (0x12C8)
RCV: INSERT on PkgNotification for PkgNotify_Add [P0100017  ][72057594037986133]  SMS_DATABASE_NOTIFICATION_MONITOR  11/18/2013 7:12:04 PM  4808 (0x12C8)
SND: Dropped C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\P0100017.PKN  [72057594037986132]  SMS_DATABASE_NOTIFICATION_MONITOR  11/18/2013 7:12:04 PM  4808 (0x12C8)
SND: Dropped C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\P0100017.PKN  [72057594037986133]  SMS_DATABASE_NOTIFICATION_MONITOR  11/18/2013 7:12:04 PM  4808 (0x12C8)

Once the PKN file is received by the distmgr will start the processing

DistMgr.log

Found notification for package 'P0100017' SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:14 PM 3604 (0x0E14)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=PRIMARY1.msdindia.com SITE=P01 PID=2656 TID=5256 GMTDATE=Mon Nov 18 13:42:15.326 2013 ISTR0="Notepad++" ISTR1="P0100017" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="P0100017" SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:15 PM 5256 (0x1488)
Start adding package to server ["Display=\\PRIMARY1.msdindia.com\"]MSWNET:["SMS_SITE=P01"]\\PRIMARY1.msdindia.com\... SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:15 PM 5256 (0x1488)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:15 PM 2924 (0x0B6C)
The distribution point is on the siteserver and the package is a content type package. There is nothing to be copied over. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:15 PM 2924 (0x0B6C)
STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=PRIMARY1.msdindia.com SITE=P01 PID=2656 TID=2924 GMTDATE=Mon Nov 18 13:42:15.881 2013 ISTR0="Notepad++" ISTR1="["Display=\\PRIMARY1.msdindia.com\"]MSWNET:["SMS_SITE=P01"]\\PRIMARY1.msdindia.com\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="P0100017" AID1=404 AVAL1="["Display=\\PRIMARY1.msdindia.com\"]MSWNET:["SMS_SITE=P01"]\\PRIMARY1.msdindia.com\" SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:15 PM 2924 (0x0B6C)
The current user context will be used for connecting to ["Display=\\PRIMARY1.msdindia.com\"]MSWNET:["SMS_SITE=P01"]\\PRIMARY1.msdindia.com\. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:16 PM 2924 (0x0B6C)
No network connection is needed to ["Display=\\PRIMARY1.msdindia.com\"]MSWNET:["SMS_SITE=P01"]\\PRIMARY1.msdindia.com\ as this is the local machine. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:16 PM 2924 (0x0B6C)
CreateSignatureShare, connecting to DP SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:16 PM 2924 (0x0B6C)
Signature share exists on distribution point path \\PRIMARY1.msdindia.com\SMSSIG$ SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:16 PM 2924 (0x0B6C)

Set share security on share \\PRIMARY1.msdindia.com\SMSSIG$ SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:16 PM 2924 (0x0B6C)
Share SMSPKGC$ exists on distribution point \\PRIMARY1.msdindia.com\SMSPKGC$ SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:16 PM 2924 (0x0B6C)
Set share security on share \\PRIMARY1.msdindia.com\SMSPKGC$ SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:16 PM 2924 (0x0B6C)
Set share security on share \\PRIMARY1.msdindia.com\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:16 PM 2924 (0x0B6C)
Set share security on share \\PRIMARY1.msdindia.com\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:16 PM 2924 (0x0B6C)
RDC:Successfully created package signature file from \\?\C:\SMSPKGSIG\P0100017.1 to \\PRIMARY1.msdindia.com\SMSSIG$\P0100017.1.tar SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:16 PM 2924 (0x0B6C)
Setting permissions on file MSWNET:["SMS_SITE=P01"]\\PRIMARY1.msdindia.com\SMSSIG$\P0100017.1.tar. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:16 PM 2924 (0x0B6C)
STATMSG: ID=2330 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=PRIMARY1.msdindia.com SITE=P01 PID=2656 TID=2924 GMTDATE=Mon Nov 18 13:42:17.021 2013 ISTR0="P0100017" ISTR1="["Display=\\PRIMARY1.msdindia.com\"]MSWNET:["SMS_SITE=P01"]\\PRIMARY1.msdindia.com\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="P0100017" AID1=404 AVAL1="["Display=\\PRIMARY1.msdindia.com\"]MSWNET:["SMS_SITE=P01"]\\PRIMARY1.msdindia.com\" SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:17 PM 2924 (0x0B6C)
StateTable::CState::Handle - (2330:1 2013-11-18 13:42:17.021+00:00) >> (2331:1 2013-11-18 13:37:40.641+00:00) SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:17 PM 2924 (0x0B6C)
CStateMsgReporter::DeliverMessages - Queued message: TT=1401 TIDT=0 TID='7F6041B0-3EE2-427F-AB72-B89610A6331C' SID=2330 MUF=0 PCNT=2, P1='P01' P2='2013-11-18 13:42:17.021+00:00' P3='' P4='' P5='' SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:17 PM 2924 (0x0B6C)
CStateMsgReporter::DeliverMessages - Created state message file: C:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\5g8vj6s1.SMX SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:17 PM 2924 (0x0B6C)
Successfully send state change notification 7F6041B0-3EE2-427F-AB72-B89610A6331C SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:17 PM 2924 (0x0B6C)
Successfully created/updated the package server in the data source SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:17 PM 2924 (0x0B6C)
Performing cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:17 PM 2924 (0x0B6C)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:17 PM 5256 (0x1488)
DP thread with thread handle 0000000000002BD0 and thread ID 2924 ended. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:17 PM 5256 (0x1488)
Package P0100017 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:17 PM 5256 (0x1488)
The package and/or program properties for package P0100017 have not changed,  need to determine which site(s) need updated package info. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:17 PM 5256 (0x1488)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=P0100017, Version=1, Status=2301 SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:17 PM 5256 (0x1488)
StoredPkgVersion (1) of package P0100017. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:17 PM 5256 (0x1488)
SourceVersion (1) of package P0100017. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:17 PM 5256 (0x1488)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=PRIMARY1.msdindia.com SITE=P01 PID=2656 TID=5256 GMTDATE=Mon Nov 18 13:42:17.588 2013 ISTR0="Notepad++" ISTR1="P0100017" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="P0100017" SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:17 PM 5256 (0x1488)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 11/18/2013 7:12:17 PM 5256 (0x1488)

In the next two parts we will cover the flow on how it goes to a remote distribution point and to distribution point in the site server (secondary site)

Hope this will be helpful in troubleshooting

Sudheesh Narayanaswamy

Content Distribution to Distribution Points -Part II

From Primary server To Secondary Server DP

Once you Add a secondary server DP from the primary server. The primary server distmgr will pickup the notification. It will then compress the contents of the package so that it can send to the site down. Content is send through the file based replication. But the instruction \ package details reaches the secondary server using DRS. Once the package is compressed it will ask the scheduler to schedule a job and the sender will the compressed file to the secondary server.

Note: The highlighted items are the checkpoints to understand the flow so that if broken we can easily find it out
Distmgr.log

Found notification for package 'P0100017' SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.31 PM 3604 (0x0E14)
Starting package processing thread, thread ID = 0xA1C (2588) SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.32 PM 3604 (0x0E14)
Needs to send the compressed package for package P0100017 to site S00 SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.34 PM 2588 (0x0A1C)
Sending a copy of package P0100017 to site S00 SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.34 PM 2588 (0x0A1C)
The reporting site of site S00 is this site. SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.34 PM 2588 (0x0A1C)
Use drive C for storing the compressed package. SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.34 PM 2588 (0x0A1C)
Set share security on share \\PRIMARY1.msdindia.com\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.34 PM 2588 (0x0A1C)
Incremented ref count on file C:\SMSPKG\P0100017.PCK.1, count = 1 SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.34 PM 2588 (0x0A1C)
Setting CMiniJob transfer root to C:\SMSPKG\P0100017.PCK.1 SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.35 PM 2588 (0x0A1C)
Incremented ref count on file C:\SMSPKG\P0100017.PCK.1, count = 2 SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.35 PM 2588 (0x0A1C)
Decremented ref count on file C:\SMSPKG\P0100017.PCK.1, count = 1 SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.35 PM 2588 (0x0A1C)
Created minijob to send compressed copy of package P0100017 to site S00.  Transfer root = C:\SMSPKG\P0100017.PCK.1. SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.35 PM 2588 (0x0A1C)
STATMSG: ID=2335 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=PRIMARY1.msdindia.com SITE=P01 PID=2656 TID=2588 GMTDATE=Mon Nov 18 14:01:35.627 2013 ISTR0="P0100017" ISTR1="S00" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="P0100017" SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.35 PM 2588 (0x0A1C)
The package and/or program properties for package P0100017 have not changed,  need to determine which site(s) need updated package info. SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.35 PM 2588 (0x0A1C)
A distribution point has been changed at this site, adding site S00 to the list of sites to which we are sending package P0100017. SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.35 PM 2588 (0x0A1C)
Parent site of S00 is P01 SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.35 PM 2588 (0x0A1C)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=P0100017, Version=1, Status=2301 SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.35 PM 2588 (0x0A1C)
StoredPkgVersion (1) of package P0100017. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.35 PM 2588 (0x0A1C)
SourceVersion (1) of package P0100017. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.35 PM 2588 (0x0A1C)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=PRIMARY1.msdindia.com SITE=P01 PID=2656 TID=2588 GMTDATE=Mon Nov 18 14:01:35.896 2013 ISTR0="Notepad++" ISTR1="P0100017" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="P0100017" SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.35 PM 2588 (0x0A1C)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 18-11-2013 7.31.35 PM 2588 (0x0A1C)

Schedule.log

<Activating JOB 000000AF> [Software Distribution for Notepad++, Package ID = P0100017] SMS_SCHEDULER 18-11-2013 7.31.45 PM 4724 (0x1274)
    Destination site:  S00, Preferred Address: *, Priority: 2 SMS_SCHEDULER 18-11-2013 7.31.45 PM 4724 (0x1274)
    Instruction type:  MICROSOFT|SMS|MINIJOBINSTRUCTION|PACKAGE SMS_SCHEDULER 18-11-2013 7.31.45 PM 4724 (0x1274)
    Creating instruction file: \\PRIMARY1.msdindia.com\SMS_P01\inboxes\schedule.box\tosend\000000AF.Id5 SMS_SCHEDULER 18-11-2013 7.31.45 PM 4724 (0x1274)
    Transfer root:  C:\SMSPKG\P0100017.PCK.1 SMS_SCHEDULER 18-11-2013 7.31.45 PM 4724 (0x1274)
    Begin to calculate signature on C:\SMSPKG\P0100017.PCK.1 SMS_SCHEDULER 18-11-2013 7.31.45 PM 4724 (0x1274)
    Signature on C:\SMSPKG\P0100017.PCK.1 is F939B4FFD923A6069445497847ED9572382E30917FB516CCC9F9D27C3317E037038821FCCBACA456356CCDDA43FBA43E18994DB3658120579355F68945B2D3C9A47687166ED3B9E434D34E673ECB3226C2AC378EF47969743D75BA3F8766DFA1B4660BC63C44A7A149B8BAE47525F9B0B9B2F05977EF17368FEC62C91B0E36075520BA34E15A1FB294F941FA0FD86B2D379CEC271089393397AF512FD327B3C580E4C695088D49EF1C4F29E42415321BE8CE0FD7F503F918E91470A962B7ACBA6F6CB678C1E274E6E08F865F9D748094732845805CF544C8CD520E29B79FA2CD2E7605BC22FFD1F5AC86418F444B90E6B4EB886B7CA6DD9FF116375DA11D3C38 SMS_SCHEDULER 18-11-2013 7.31.45 PM 4724 (0x1274)
    Hash algorithm ID on C:\SMSPKG\P0100017.PCK.1 is 0x800C SMS_SCHEDULER 18-11-2013 7.31.45 PM 4724 (0x1274)
    Instruction (and package) file created.  Mark job active. SMS_SCHEDULER 18-11-2013 7.31.45 PM 4724 (0x1274)
    <JOB STATUS - ACTIVE> SMS_SCHEDULER 18-11-2013 7.31.45 PM 4724 (0x1274)

Sender.log

Package file = C:\SMSPKG\P0100017.PCK.1 SMS_LAN_SENDER 18-11-2013 7.32.00 PM 1460 (0x05B4)
Instruction file = C:\Program Files\Microsoft Configuration Manager\inboxes\schedule.box\tosend\000000AF.Id5 SMS_LAN_SENDER 18-11-2013 7.32.00 PM 1460 (0x05B4)
Checking for remote file \\SECONDARY1.msdindia.com\SMS_SITE\2004VP01.PCK SMS_LAN_SENDER 18-11-2013 7.32.00 PM 1460 (0x05B4)
Checking for remote file \\SECONDARY1.msdindia.com\SMS_SITE\2004VP01.SNI SMS_LAN_SENDER 18-11-2013 7.32.00 PM 1460 (0x05B4)
Checking for remote file \\SECONDARY1.msdindia.com\SMS_SITE\2004VP01.TMP SMS_LAN_SENDER 18-11-2013 7.32.00 PM 1460 (0x05B4)
Attempt to create/open the remote file \\SECONDARY1.msdindia.com\SMS_SITE\2004VP01.PCK SMS_LAN_SENDER 18-11-2013 7.32.00 PM 1460 (0x05B4)
Created/opened the remote file \\SECONDARY1.msdindia.com\SMS_SITE\2004VP01.PCK SMS_LAN_SENDER 18-11-2013 7.32.00 PM 1460 (0x05B4)
Attempt to create/open the remote file \\SECONDARY1.msdindia.com\SMS_SITE\2004VP01.PCK SMS_LAN_SENDER 18-11-2013 7.32.00 PM 1460 (0x05B4)
Created/opened the remote file \\SECONDARY1.msdindia.com\SMS_SITE\2004VP01.PCK SMS_LAN_SENDER 18-11-2013 7.32.00 PM 1460 (0x05B4)
…………………………………………………….
Attempt to write 665600 bytes to \\SECONDARY1.msdindia.com\SMS_SITE\2004VP01.PCK at position 66560 SMS_LAN_SENDER 18-11-2013 7.32.00 PM 1460 (0x05B4)
Wrote 65536 bytes to \\SECONDARY1.msdindia.com\SMS_SITE\2004VP01.PCK at position 1024 SMS_LAN_SENDER 18-11-2013 7.32.00 PM 1460 (0x05B4)
Wrote 665600 bytes to \\SECONDARY1.msdindia.com\SMS_SITE\2004VP01.PCK at position 66560 SMS_LAN_SENDER 18-11-2013 7.32.00 PM 1460 (0x05B4)
Attempt to write 1048576 bytes to \\SECONDARY1.msdindia.com\SMS_SITE\2004VP01.PCK at position 732160 SMS_LAN_SENDER 18-11-2013 7.32.00 PM 1460 (0x05B4)
Wrote 1048576 bytes to \\SECONDARY1.msdindia.com\SMS_SITE\2004VP01.PCK at position 732160 SMS_LAN_SENDER 18-11-2013 7.32.01 PM 1460 (0x05B4)

We see here that the PCK file which is compressed content and the instruction file .ID5 created by the scheduler is send to the secondary. The instruction file helps the despooler at the secondary to understand what to do with the PCK file received.

Till the package reaches the server you will find the package status in in progress mode

Secondary Server

In the secondary server \inboxes\despoolr.box\receive which is SMS_SITE share receive the content.  When it is being processed you might failed to execute if the DRS replication delay is there as the package information comes through DRS. You can confirm this running the query

You could see in the above result that the secondary server has not got the information w.r.t to secondary server for type 1.

Despool.log

Signature checked out OK for instruction coming from site P01, proceed with the instruction execution. SMS_DESPOOLER 18-11-2013 7.32.05 PM 2208 (0x08A0)
Executing instruction of type MICROSOFT|SMS|MINIJOBINSTRUCTION|PACKAGE SMS_DESPOOLER 18-11-2013 7.32.05 PM 2208 (0x08A0)
Received package P0100017 version 1. Compressed file -  C:\SMSPKG\P0100017.PCK.1 as C:\Program Files\Microsoft Configuration Manager\inboxes\despoolr.box\receive\ds_s916k.pkg SMS_DESPOOLER 18-11-2013 7.32.05 PM 2208 (0x08A0)
This package[P0100017]'s information hasn't arrived yet for this version [1]. Retry later ... SMS_DESPOOLER 18-11-2013 7.32.06 PM 2208 (0x08A0)
Despooler failed to execute the instruction, error code = 12 SMS_DESPOOLER 18-11-2013 7.32.06 PM 2208 (0x08A0)

Once the information reaches the secondary server database you will find this. And in the next retry you will find the instruction getting proceeded. Once the instruction is processed the package will be uncompressed  

Despool.log

Verifying signature for instruction C:\Program Files\Microsoft Configuration Manager\inboxes\despoolr.box\receive\ds_lofhs.nil of type MICROSOFT|SMS|MINIJOBINSTRUCTION|PACKAGE SMS_DESPOOLER 18-11-2013 7.37.16 PM 3416 (0x0D58)
Signature checked out OK for instruction coming from site P01, proceed with the instruction execution. SMS_DESPOOLER 18-11-2013 7.37.16 PM 3416 (0x0D58)
Executing instruction of type MICROSOFT|SMS|MINIJOBINSTRUCTION|PACKAGE SMS_DESPOOLER 18-11-2013 7.37.16 PM 3416 (0x0D58)
STATMSG: ID=4407 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DESPOOLER" SYS=SECONDARY1.msdindia.com SITE=S00 PID=2700 TID=3416 GMTDATE=Mon Nov 18 14:07:16.286 2013 ISTR0="P0100017" ISTR1="1" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="P0100017" SMS_DESPOOLER 18-11-2013 7.37.16 PM 3416 (0x0D58)
Received package P0100017 version 1. Compressed file -  C:\SMSPKG\P0100017.PCK.1 as C:\Program Files\Microsoft Configuration Manager\inboxes\despoolr.box\receive\PKGs15lf.TRY SMS_DESPOOLER 18-11-2013 7.37.16 PM 3416 (0x0D58)
Old package storedUNC path is . SMS_DESPOOLER 18-11-2013 7.37.16 PM 3416 (0x0D58)
Use drive C for storing the compressed package. SMS_DESPOOLER 18-11-2013 7.37.16 PM 3416 (0x0D58)
No branch cache registry entries found. SMS_DESPOOLER 18-11-2013 7.37.17 PM 3416 (0x0D58)
Uncompressing C:\SMSPKG\P0100017.PCK to C:\SMSPKG\P0100017.PCK.temp SMS_DESPOOLER 18-11-2013 7.37.17 PM 3416 (0x0D58)
Content Library: C:\SCCMContentLib SMS_DESPOOLER 18-11-2013 7.37.17 PM 3416 (0x0D58)
Extracting from C:\SMSPKG\P0100017.PCK.temp SMS_DESPOOLER 18-11-2013 7.37.17 PM 3416 (0x0D58)
Extracting package P0100017 SMS_DESPOOLER 18-11-2013 7.37.17 PM 3416 (0x0D58)
Extracting content P0100017.1 SMS_DESPOOLER 18-11-2013 7.37.17 PM 3416 (0x0D58)
Package P0100017 (version 0) exists in the distribution source, save the newer version (version 1). SMS_DESPOOLER 18-11-2013 7.37.20 PM 3416 (0x0D58)
Stored Package P0100017. Stored Package Version = 1 SMS_DESPOOLER 18-11-2013 7.37.20 PM 3416 (0x0D58)
STATMSG: ID=4400 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DESPOOLER" SYS=SECONDARY1.msdindia.com SITE=S00 PID=2700 TID=3416 GMTDATE=Mon Nov 18 14:07:21.599 2013 ISTR0="P0100017" ISTR1="\\SECONDARY1.msdindia.com\C$\SMSPKG\P0100017.PCK" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="P0100017" SMS_DESPOOLER 18-11-2013 7.37.21 PM 3416 (0x0D58)
Despooler successfully executed one instruction. SMS_DESPOOLER 18-11-2013 7.37.21 PM 3416 (0x0D58)

The secondary server distmgr now will pick this notification and start processing the package

Distmgr.log

Found notification for package 'P0100017' SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.41 PM 3308 (0x0CEC)
Start updating the package P0100017... SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.42 PM 3688 (0x0E68)
The Package Action is 1, the Update Mask is 160 and UpdateMaskEx is 0. SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.42 PM 3688 (0x0E68)
Use drive C for storing the compressed package. SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.42 PM 3688 (0x0E68)
Successfully created/updated the package P0100017 SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.42 PM 3688 (0x0E68)
STATMSG: ID=2311 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SECONDARY1.msdindia.com SITE=S00 PID=2700 TID=3688 GMTDATE=Mon Nov 18 14:07:42.411 2013 ISTR0="P0100017" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="P0100017" SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.42 PM 3688 (0x0E68)
Set share security on share \\SECONDARY1.msdindia.com\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.42 PM 3688 (0x0E68)
Start adding package to server ["Display=\\SECONDARY1.msdindia.com\"]MSWNET:["SMS_SITE=S00"]\\SECONDARY1.msdindia.com\... SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.43 PM 3688 (0x0E68)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.43 PM 2856 (0x0B28)
The distribution point is on the siteserver and the package is a content type package. There is nothing to be copied over. SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.43 PM 2856 (0x0B28)
STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SECONDARY1.msdindia.com SITE=S00 PID=2700 TID=2856 GMTDATE=Mon Nov 18 14:07:43.521 2013 ISTR0="Notepad++" ISTR1="["Display=\\SECONDARY1.msdindia.com\"]MSWNET:["SMS_SITE=S00"]\\SECONDARY1.msdindia.com\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="P0100017" AID1=404 AVAL1="["Display=\\SECONDARY1.msdindia.com\"]MSWNET:["SMS_SITE=S00"]\\SECONDARY1.msdindia.com\" SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.43 PM 2856 (0x0B28)
\\?\C:\SMSPKGSIG\P0100017.1 could not be located SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.43 PM 2856 (0x0B28)
Set share security on share \\SECONDARY1.msdindia.com\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.43 PM 2856 (0x0B28)
The current user context will be used for connecting to ["Display=\\SECONDARY1.msdindia.com\"]MSWNET:["SMS_SITE=S00"]\\SECONDARY1.msdindia.com\. SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.44 PM 2856 (0x0B28)
No network connection is needed to ["Display=\\SECONDARY1.msdindia.com\"]MSWNET:["SMS_SITE=S00"]\\SECONDARY1.msdindia.com\ as this is the local machine. SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.44 PM 2856 (0x0B28)
CreateSignatureShare, connecting to DP SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.44 PM 2856 (0x0B28)Signature share exists on distribution point path \\SECONDARY1.msdindia.com\SMSSIG$ SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.44 PM 2856 (0x0B28)
Set share security on share \\SECONDARY1.msdindia.com\SMSSIG$ SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.44 PM 2856 (0x0B28)
Share SMSPKGC$ exists on distribution point \\SECONDARY1.msdindia.com\SMSPKGC$ SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.44 PM 2856 (0x0B28)
Set share security on share \\SECONDARY1.msdindia.com\SMSPKGC$ SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.44 PM 2856 (0x0B28)
Creating, reading and or updating Operations Management server role registry keys for a Distribution Point ... SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.44 PM 2856 (0x0B28)
Set share security on share \\SECONDARY1.msdindia.com\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.44 PM 2856 (0x0B28)
Set share security on share \\SECONDARY1.msdindia.com\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.44 PM 2856 (0x0B28)
RDC:Successfully created package signature file from \\?\C:\SMSPKGSIG\P0100017.1 to \\SECONDARY1.msdindia.com\SMSSIG$\P0100017.1.tar SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.44 PM 2856 (0x0B28)
Setting permissions on file MSWNET:["SMS_SITE=S00"]\\SECONDARY1.msdindia.com\SMSSIG$\P0100017.1.tar. SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.44 PM 2856 (0x0B28)
STATMSG: ID=2330 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SECONDARY1.msdindia.com SITE=S00 PID=2700 TID=2856 GMTDATE=Mon Nov 18 14:07:44.802 2013 ISTR0="P0100017" ISTR1="["Display=\\SECONDARY1.msdindia.com\"]MSWNET:["SMS_SITE=S00"]\\SECONDARY1.msdindia.com\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="P0100017" AID1=404 AVAL1="["Display=\\SECONDARY1.msdindia.com\"]MSWNET:["SMS_SITE=S00"]\\SECONDARY1.msdindia.com\" SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.44 PM 2856 (0x0B28)
Successfully created/updated the package server in the data source SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.44 PM 2856 (0x0B28)
Package P0100017 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.45 PM 3688 (0x0E68)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=P0100017, Version=1, Status=2301 SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.45 PM 3688 (0x0E68)
StoredPkgVersion (1) of package P0100017. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.45 PM 3688 (0x0E68)
SourceVersion (1) of package P0100017. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.45 PM 3688 (0x0E68)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SECONDARY1.msdindia.com SITE=S00 PID=2700 TID=3688 GMTDATE=Mon Nov 18 14:07:45.505 2013 ISTR0="Notepad++" ISTR1="P0100017" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="P0100017" SMS_DISTRIBUTION_MANAGER 18-11-2013 7.37.45 PM 3688 (0x0E68)

Once the package is distributed successfully the secondary site DB is updated with the pkgstatus and the same reaches the primary through DRS and then you can see the status changing from in progress to success.

Hope this helps in tracking the flow on distributing a package to secondary server DP

Sudheesh Narayanaswamy

Support Escalation Engineer

This is a very common topic I am getting with my education customers and student labs, etc. My colleague James Baker created this excellent post:

Using Student Advantage with Remote Desktop Session Host (RDSH), Virtual Desktop Infrastructure (VDI) , and Electronic Software Distribution (ESD) systems.

With the launch of Student Advantage there are many questions customers have around using the Office 365 Pro Plus install within different environments that may have previously depended on a MSI model.  Rest assured there are solutions for you RDSH, VDI and ESD scenarios with Student Advantage.

Electronic Software Distribution (ESD) systems.

All Electronic Software Distribution can work to deploy Office 365 ProPlus. The ESD just runs a setup.exe bootstrapper (from the Office Deployment Tool for Click-to-Run) at the end of the day, more or less like the Office MSI package or anything software that installs via an EXE.  You can find more information on deploying with the Office Deployment Tool for Click-To-Run here

Remote Desktop Session Host (RDSH)

You’ll need to use a Volume Activation package (Office Professional Plus or Standard 2013) to install on the server with the RDS role enabled.  More information can be found here in a blog post by my co-worker BVA who spoke about this install for the O365 E SKUs

Virtual Desktop Infrastructure (VDI)

For VDI architectures where each student has a dedicated virtual machine (aka Personal VM), normal Office 365 ProPlus works as long as that machine meets system requirements and periodically connects to the Internet to validate the user’s subscription.

For VDI architectures where there are shared machines (aka Pooled VM) you’ll need to use a Volume Activation package (Office Professional Plus or Standard 2013) to install on the machine.  Same scenario as the RDSH scenario above. 

______

I also found an excellent Office Garage Series video going through these Office 365 ProPlus deployment scenarios along with App-V deployment of Office 365 ProPlus here or click below:

Merhaba TechNet Wiki Ailesi

            Yine bir pazar günü supriziyle birlikteyiz. Bugün paylaşacağım yazı aslında hemen hepinizin bilmiş olduğu bir yazı ama bu güzel haberi defalarca paylaşmaktan gurur duyuyorum. Geçen zamanlarda biliyorsunuz ki TechNet Wiki üzerinde Gokan Ayın MVP'si seçilmişti. (ilgili haberin detaylarına buradan ulaşabilirsiniz.) Kendisini tekrar tebrik ediyorum. Ama Gokan hakkında şu sözleri söylemeden de duramayacağım. Ben bazen Gokan'ın insan olduğuna şüpheleniyorum. Bu kadar azimli çalışması ve istekli çalışması gerçekten taktire şayan bir durum. Sadece Türk Konseyinin lideri değil. Fransız topluluğununda bir parçası zaten aşağıda sizlerle  paylaşacağım linklerde sizde Gokan'ın ne kadar azimli ve istekli çalıştığını göreceksiniz.  Bunun yanında bugün yine Wikininjas üzerinde bir makale yayınladı makale konusuna gelince First WikiNinjas eBook yani Wikininja ekibinin ilk E-kitabını yazarı. İlgili habere ulaşmak için tıklayınız.  

Profil : Gokan Ozcifci

Gokan İleri ki zamanlarda karşımıza ne gibi projelerle çıkacak bakalım. Merakla bekliyoruz. Kendisini tekrar tebrik eder başarılarının devamını dilerim. 

Content Distribution to Distribution Points -Part III

From primary site to Remote distribution Point

In 2012 the flow is different from 2007 when a package is distributed to a remote DP. We have the new component PACKAGE TRANSFER MANAGER in 2012. The top level flow is that the distmgr get the request and when it is a remote DP it will ask the package transfer manager to copy the contents to the remote DP.  The flow is below

Once you add the remote DP from console, the notification file is dropped by smsdbmon. Distmgr takes this nofication and start processing the package.
As it is a remote DP the distmgr will create a package transefer job to send compressed copy of package.

The Package transfer Manager updates the status using the state messages along with status messages.

Note: The highlighted items are the checkpoints to understand the flow so that if broken we can easily find it out

smsdbmon.log

Next time check will be at Tuesday 11/19/2013 06:00:24 SMS_DATABASE_NOTIFICATION_MONITOR 19-11-2013 5.00.26 AM 2284 (0x08EC)
RCV: INSERT on PkgNotification for PkgNotify_Add [PR100006  ][72057594037968540] SMS_DATABASE_NOTIFICATION_MONITOR 19-11-2013 5.00.44 AM 2148 (0x0864)
RCV: INSERT on PkgNotification for PkgNotify_Add [PR100006  ][72057594037968541] SMS_DATABASE_NOTIFICATION_MONITOR 19-11-2013 5.00.44 AM 2148 (0x0864)
SND: Dropped C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\PR100006.PKN  [72057594037968540] SMS_DATABASE_NOTIFICATION_MONITOR 19-11-2013 5.00.44 AM 2148 (0x0864)
SND: Dropped C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\PR100006.PKN  [72057594037968541] SMS_DATABASE_NOTIFICATION_MONITOR 19-11-2013 5.00.44 AM 2148 (0x0864)

distmgr.log

Found notification for package 'PR100006' SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.54 AM 2776 (0x0AD8)
Used 0 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.55 AM 2776 (0x0AD8)
Starting package processing thread, thread ID = 0xB64 (2916) SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.55 AM 2776 (0x0AD8)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.55 AM 2776 (0x0AD8)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=CMLABPR1.CMLAB.COM SITE=PR1 PID=4676 TID=2916 GMTDATE=Tue Nov 19 13:00:55.122 2013 ISTR0="Package1" ISTR1="PR100006" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="PR100006" SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.55 AM 2916 (0x0B64)
No action specified for the package PR100006. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.55 AM 2916 (0x0B64)
Start adding package to server ["Display=\\CMLABWIN71.CMLAB.COM\"]MSWNET:["SMS_SITE=PR1"]\\CMLABWIN71.CMLAB.COM\... SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.55 AM 2916 (0x0B64)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.55 AM 5032 (0x13A8)
Will wait for 1 threads to end. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.55 AM 2916 (0x0B64)
Thread Handle = 0000000000001B94 SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.55 AM 2916 (0x0B64)
STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=CMLABPR1.CMLAB.COM SITE=PR1 PID=4676 TID=5032 GMTDATE=Tue Nov 19 13:00:55.359 2013 ISTR0="Package1" ISTR1="["Display=\\CMLABWIN71.CMLAB.COM\"]MSWNET:["SMS_SITE=PR1"]\\CMLABWIN71.CMLAB.COM\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="PR100006" AID1=404 AVAL1="["Display=\\CMLABWIN71.CMLAB.COM\"]MSWNET:["SMS_SITE=PR1"]\\CMLABWIN71.CMLAB.COM\" SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.55 AM 5032 (0x13A8)
The current user context will be used for connecting to ["Display=\\CMLABWIN71.CMLAB.COM\"]MSWNET:["SMS_SITE=PR1"]\\CMLABWIN71.CMLAB.COM\. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.55 AM 5032 (0x13A8)
Successfully made a network connection to \\CMLABWIN71.CMLAB.COM\ADMIN$. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.55 AM 5032 (0x13A8)
Signature share exists on distribution point path \\CMLABWIN71.CMLAB.COM\SMSSIG$ SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.55 AM 5032 (0x13A8)
Share SMSPKGC$ exists on distribution point \\CMLABWIN71.CMLAB.COM\SMSPKGC$ SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.55 AM 5032 (0x13A8)
Creating, reading and or updating Operations Management server role registry keys for a Distribution Point ... SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.56 AM 5032 (0x13A8)
Creating, reading or updating IIS registry key for a distribution point. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.56 AM 5032 (0x13A8)
IISPortsList in the SCF is "80". SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.56 AM 5032 (0x13A8)
IISSSLPortsList in the SCF is "443". SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.56 AM 5032 (0x13A8)
IISWebSiteName in the SCF is "". SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.56 AM 5032 (0x13A8)
IISSSLState in the SCF is 480. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.56 AM 5032 (0x13A8)
CWmiRegistry::GetStr: Failed to get string value SCFSSLPortList SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.56 AM 5032 (0x13A8)
CWmiRegistry::GetStr: Failed to get string value SMSSSLPortList SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.56 AM 5032 (0x13A8)
CWmiRegistry::GetStr: Failed to get string value SMSCWSPortList SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.56 AM 5032 (0x13A8)
CWmiRegistry::GetStr: Failed to get string value SMSCWSSSLPortList SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.57 AM 5032 (0x13A8)
Virtual Directory SMS_DP_SMSPKG$ for the physical path C:\SCCMContentLib already exists. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.57 AM 5032 (0x13A8)
STATMSG: ID=2375 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=CMLABPR1.CMLAB.COM SITE=PR1 PID=4676 TID=5032 GMTDATE=Tue Nov 19 13:00:57.225 2013 ISTR0="["Display=\\CMLABWIN71.CMLAB.COM\"]MSWNET:["SMS_SITE=PR1"]\\CMLABWIN71.CMLAB.COM\" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\CMLABWIN71.CMLAB.COM\"]MSWNET:["SMS_SITE=PR1"]\\CMLABWIN71.CMLAB.COM\" SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.57 AM 5032 (0x13A8)
Creating, reading or updating IIS registry key for a distribution point. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.57 AM 5032 (0x13A8)
IISPortsList in the SCF is "80". SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.57 AM 5032 (0x13A8)
IISSSLPortsList in the SCF is "443". SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.57 AM 5032 (0x13A8)
IISWebSiteName in the SCF is "". SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.57 AM 5032 (0x13A8)
IISSSLState in the SCF is 480. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.57 AM 5032 (0x13A8)
CWmiRegistry::GetStr: Failed to get string value SCFSSLPortList SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.57 AM 5032 (0x13A8)
CWmiRegistry::GetStr: Failed to get string value SMSSSLPortList SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.57 AM 5032 (0x13A8)
CWmiRegistry::GetStr: Failed to get string value SMSCWSPortList SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.57 AM 5032 (0x13A8)
CWmiRegistry::GetStr: Failed to get string value SMSCWSSSLPortList SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.57 AM 5032 (0x13A8)
Virtual Directory SMS_DP_SMSSIG$ for the physical path C:\SMSSIG$ already exists. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.57 AM 5032 (0x13A8)
STATMSG: ID=2375 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=CMLABPR1.CMLAB.COM SITE=PR1 PID=4676 TID=5032 GMTDATE=Tue Nov 19 13:00:57.727 2013 ISTR0="["Display=\\CMLABWIN71.CMLAB.COM\"]MSWNET:["SMS_SITE=PR1"]\\CMLABWIN71.CMLAB.COM\" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\CMLABWIN71.CMLAB.COM\"]MSWNET:["SMS_SITE=PR1"]\\CMLABWIN71.CMLAB.COM\" SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.57 AM 5032 (0x13A8)
Created package transefer job to send compressed copy of package PR100006 to distribution point ["Display=\\CMLABWIN71.CMLAB.COM\"]MSWNET:["SMS_SITE=PR1"]\\CMLABWIN71.CMLAB.COM\.  Transfer root = PR100006.PCK.DLT.0.1. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.58 AM 5032 (0x13A8)
JobID = JENK71H9 SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.58 AM 5032 (0x13A8)
STATMSG: ID=2357 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=CMLABPR1.CMLAB.COM SITE=PR1 PID=4676 TID=5032 GMTDATE=Tue Nov 19 13:00:58.392 2013 ISTR0="PR100006" ISTR1="["Display=\\CMLABWIN71.CMLAB.COM\"]MSWNET:["SMS_SITE=PR1"]\\CMLABWIN71.CMLAB.COM\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="PR100006" AID1=404 AVAL1="["Display=\\CMLABWIN71.CMLAB.COM\"]MSWNET:["SMS_SITE=PR1"]\\CMLABWIN71.CMLAB.COM\" SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.58 AM 5032 (0x13A8)
Performing cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.58 AM 5032 (0x13A8)
Cancelling network connection to \\CMLABWIN71.CMLAB.COM\ADMIN$. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.58 AM 5032 (0x13A8)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.58 AM 2916 (0x0B64)
DP thread with thread handle 0000000000001B94 and thread ID 5032 ended. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.58 AM 2916 (0x0B64)
Updating package info for package PR100006 SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.58 AM 2916 (0x0B64)
Package PR100006 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.58 AM 2916 (0x0B64)
The package and/or program properties for package PR100006 have not changed,  need to determine which site(s) need updated package info. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.58 AM 2916 (0x0B64)
StoredPkgVersion (1) of package PR100006. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.58 AM 2916 (0x0B64)
SourceVersion (1) of package PR100006. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.58 AM 2916 (0x0B64)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=CMLABPR1.CMLAB.COM SITE=PR1 PID=4676 TID=2916 GMTDATE=Tue Nov 19 13:00:58.830 2013 ISTR0="Package1" ISTR1="PR100006" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="PR100006" SMS_DISTRIBUTION_MANAGER 19-11-2013 5.00.58 AM 2916 (0x0B64)

Packagexfermgr

========  Starting Processing Cycle ( 19-11-2013 05:01:08 Pacific Standard Time) ======== SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.08 AM 3844 (0x0F04)
========  Processing Jobs  ======== SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.08 AM 3844 (0x0F04)
Activating job JENK71H9, for package PR100006 version 1, Distribution point :  CMLABWIN71.CMLAB.COM, Priority: 2 SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.09 AM 3844 (0x0F04)
    Need to send package file (PR100006.PCK.DLT.0.1) SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.09 AM 3844 (0x0F04)
Updating job JENK71H9 SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.10 AM 3844 (0x0F04)
    Created new send request ID:  20003PR1 SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.10 AM 3844 (0x0F04)
Job count is 1. SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.23 AM 3844 (0x0F04)
====  Found 1 send requests in outbox C:\Program Files\Microsoft Configuration Manager\inboxes\PkgTransferMgr.box\requests. SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.23 AM 3844 (0x0F04)
Send Request 20003PR1~    Job:        JENK71H9  Destination:  CMLABWIN71.CMLAB.COM~    State:      Pending   Status:               Action:    None~    Total size: 0       k Remaining: 0       k Heartbeat: 05:01~    Start:      12:00     Finish:    12:00      Retry:     05:01~    SWD PkgID:  PR100006  SWD Pkg Version: 1 SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.23 AM 3844 (0x0F04)
====  Checking send requests for outbox C:\Program Files\Microsoft Configuration Manager\inboxes\PkgTransferMgr.box\requests. SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.23 AM 3844 (0x0F04)
    Checking unscheduled send request 20003PR1 SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.23 AM 3844 (0x0F04)
========  Finished Processing Cycle ( 19-11-2013 05:01:24 Pacific Standard Time) ======== SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.24 AM 3844 (0x0F04)

Found send request.  ID: 20003PR1, Destination: CMLABWIN71.CMLAB.COM SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.28 AM 2864 (0x0B30)
We have 0 active connections SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.28 AM 2864 (0x0B30)
Checking for sitesystem-specific sending capacity.  Used 0 out of 5. SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.28 AM 2864 (0x0B30)
We have 0 active connections SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.28 AM 2864 (0x0B30)
Created sending thread (Thread ID = 0x1204) SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.28 AM 2864 (0x0B30)

Sending thread starting SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.28 AM 4612 (0x1204)
Package file = PR100006.PCK.DLT.0.1 SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.28 AM 4612 (0x1204)
Performing preactions package PR100006, Distribution point CMLABWIN71.CMLAB.COM SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.28 AM 4612 (0x1204)
Sending legacy content PR100006.1 for package PR100006 SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.28 AM 4612 (0x1204)
Redistribute=0, Related= SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.28 AM 4612 (0x1204)
Created/opened the remote file \\CMLABWIN71.CMLAB.COM\SMS_DP$\PR100006.1-93596791AF1B0225B1E0DE36E08E3673A523A89C037988AD8C2D1840DF9E84F9 SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.28 AM 4612 (0x1204)
Sending Started [C:\SCCMContentLib\FileLib\9359\93596791AF1B0225B1E0DE36E08E3673A523A89C037988AD8C2D1840DF9E84F9] SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.28 AM 4612 (0x1204)
Attempt to write 5120 bytes to \\CMLABWIN71.CMLAB.COM\SMS_DP$\PR100006.1-93596791AF1B0225B1E0DE36E08E3673A523A89C037988AD8C2D1840DF9E84F9 at position 0 SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.28 AM 4612 (0x1204)
Wrote 5120 bytes to \\CMLABWIN71.CMLAB.COM\SMS_DP$\PR100006.1-93596791AF1B0225B1E0DE36E08E3673A523A89C037988AD8C2D1840DF9E84F9 at position 0 SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.28 AM 4612 (0x1204)
Attempt to write 102400 bytes to \\CMLABWIN71.CMLAB.COM\SMS_DP$\PR100006.1-93596791AF1B0225B1E0DE36E08E3673A523A89C037988AD8C2D1840DF9E84F9 at position 5120 SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.28 AM 4612 (0x1204)
Wrote 102400 bytes to \\CMLABWIN71.CMLAB.COM\SMS_DP$\PR100006.1-93596791AF1B0225B1E0DE36E08E3673A523A89C037988AD8C2D1840DF9E84F9 at position 5120 SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.29 AM 4612 (0x1204)
Attempt to write 738176 bytes to \\CMLABWIN71.CMLAB.COM\SMS_DP$\PR100006.1-93596791AF1B0225B1E0DE36E08E3673A523A89C037988AD8C2D1840DF9E84F9 at position 107520 SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.29 AM 4612 (0x1204)
Wrote 738176 bytes to \\CMLABWIN71.CMLAB.COM\SMS_DP$\PR100006.1-93596791AF1B0225B1E0DE36E08E3673A523A89C037988AD8C2D1840DF9E84F9 at position 107520 SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.29 AM 4612 (0x1204)
We have 1 active connections SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.33 AM 2864 (0x0B30)
Checking for sending capacity.  Used 1 out of 15. SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.33 AM 2864 (0x0B30)

Waiting for new/rescheduled send requests, Maximum Sleep Time = 60 minutes SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.33 AM 2864 (0x0B30)
Sending completed [C:\SCCMContentLib\FileLib\9359\93596791AF1B0225B1E0DE36E08E3673A523A89C037988AD8C2D1840DF9E84F9] SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.34 AM 4612 (0x1204)
Completed post-actions for remote DP CMLABWIN71.CMLAB.COM SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.36 AM 4612 (0x1204)
Sending completed successfully SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.36 AM 4612 (0x1204)

Deleting remote file 20003PR1.PCK SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.36 AM 4612 (0x1204)
Notifying pkgXferJobMgr SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.36 AM 4612 (0x1204)
COutbox::TakeNextToSend(pszSiteCode) SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.36 AM 4612 (0x1204)
Finished sending SWD package PR100006 version 1 to distribution point CMLABWIN71.CMLAB.COM SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.36 AM 4612 (0x1204)
STATMSG: ID=8200 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=CMLABPR1.CMLAB.COM SITE=PR1 PID=4676 TID=4612 GMTDATE=Tue Nov 19 13:01:36.429 2013 ISTR0="PR100006" ISTR1="1" ISTR2="CMLABWIN71.CMLAB.COM" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="PR100006" AID1=410 AVAL1="1" SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.36 AM 4612 (0x1204)
Sent status to the distribution manager for pkg PR100006, version 1, status 3 and distribution point ["Display=\\CMLABWIN71.CMLAB.COM\"]MSWNET:["SMS_SITE=PR1"]\\CMLABWIN71.CMLAB.COM\ SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.36 AM 4612 (0x1204)
STATMSG: ID=8210 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=CMLABPR1.CMLAB.COM SITE=PR1 PID=4676 TID=4612 GMTDATE=Tue Nov 19 13:01:36.826 2013 ISTR0="PR100006" ISTR1="1" ISTR2="CMLABWIN71.CMLAB.COM" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="PR100006" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\CMLABWIN71.CMLAB.COM\"]MSWNET:["SMS_SITE=PR1"]\\CMLABWIN71.CMLAB.COM\" SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.36 AM 4612 (0x1204)
StateTable::CState::Handle - (8210:1 2013-11-19 13:01:36.826+00:00) >> (0:0 2013-11-18 12:39:08.445+00:00) SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.36 AM 4612 (0x1204)
CStateMsgReporter::DeliverMessages - Queued message: TT=1401 TIDT=0 TID='7F6041B0-3EE2-427F-AB72-B89610A6331C' SID=8210 MUF=0 PCNT=2, P1='PR1' P2='2013-11-19 13:01:36.826+00:00' P3='' P4='' P5='' SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.36 AM 4612 (0x1204)
CStateMsgReporter::DeliverMessages - Created state message file: C:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\qa2ma8pt.SMX SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.38 AM 4612 (0x1204)
Successfully send state change notification 7F6041B0-3EE2-427F-AB72-B89610A6331C SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.38 AM 4612 (0x1204)
Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.38 AM 4612 (0x1204)
We have 0 active connections SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.38 AM 2864 (0x0B30)
Checking for sending capacity.  Used 0 out of 15. SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.38 AM 2864 (0x0B30)
COutbox::TakeNextToSend(pszSiteCode) SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.38 AM 2864 (0x0B30)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.38 AM 2864 (0x0B30)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 60 minutes SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.38 AM 2864 (0x0B30)
DeleteNotificationFiles deleted 1 *.DWS file(s) this cycle. SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.46 AM 3844 (0x0F04)

========  Starting Processing Cycle ( 19-11-2013 05:01:46 Pacific Standard Time) ======== SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.46 AM 3844 (0x0F04)
========  Processing Jobs  ======== SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.46 AM 3844 (0x0F04)
Updating job JENK71H9 SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.46 AM 3844 (0x0F04)
Job count is 1. SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.57 AM 3844 (0x0F04)
====  Found 1 send requests in outbox \\CMLABPR1.CMLAB.COM\SMS_PR1\inboxes\PkgTransferMgr.box\outboxes\LAN. SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.57 AM 3844 (0x0F04)
Send Request 20003PR1~    Job:        JENK71H9  Destination:  CMLABWIN71.CMLAB.COM~    State:      Working   Status:    Success    Action:    None~    Total size: 0       k Remaining: 0       k Heartbeat: 05:01~    Start:      05:01     Finish:    05:01      Retry:          ~    SWD PkgID:  PR100006  SWD Pkg Version: 1 SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.58 AM 3844 (0x0F04)
====  Checking send requests for outbox \\CMLABPR1.CMLAB.COM\SMS_PR1\inboxes\PkgTransferMgr.box\outboxes\LAN. SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.58 AM 3844 (0x0F04)
    Checking send request 20003PR1 SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.58 AM 3844 (0x0F04)
        Sending completed (0 bytes/sec). SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.58 AM 3844 (0x0F04)
========  Finished Processing Cycle ( 19-11-2013 05:01:58 Pacific Standard Time) ======== SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.58 AM 3844 (0x0F04)
Sleeping for maximum 10000 seconds. SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.01.58 AM 3844 (0x0F04)
========  Starting Processing Cycle ( 19-11-2013 05:02:08 Pacific Standard Time) ======== SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.02.08 AM 3844 (0x0F04)
========  Processing Jobs  ======== SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.02.08 AM 3844 (0x0F04)
Updating job JENK71H9 SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.02.09 AM 3844 (0x0F04)
    Send request was PENDING, now ACTIVE. SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.02.10 AM 3844 (0x0F04)
    Send request has successfully completed. SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.02.10 AM 3844 (0x0F04)
    <JOB STATUS - COMPLETE> SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.02.10 AM 3844 (0x0F04)
    Deleting send request with ID: 20003PR1. SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.02.10 AM 3844 (0x0F04)
    Deleted job JENK71H9. SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.02.10 AM 3844 (0x0F04)
We have 0 active connections SMS_PACKAGE_TRANSFER_MANAGER 19-11-2013 5.02.15 AM 2864 (0x0B30)

One the remote DP you can see

smsdpprov.log

[8C4][Tue 11/19/2013 18:31:36]:Conent 'PR100006.1' for package 'PR100006' has been added to content library successfully

distmgr.log

Processing incoming file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\FXIYWOCM.STA. SMS_DISTRIBUTION_MANAGER 19-11-2013 5.01.41 AM 328 (0x0148)
Processing STA for regular DP ["Display=\\CMLABWIN71.CMLAB.COM\"]MSWNET:["SMS_SITE=PR1"]\\CMLABWIN71.CMLAB.COM\ SMS_DISTRIBUTION_MANAGER 19-11-2013 5.01.41 AM 328 (0x0148)
Processing status update for package PR100006 SMS_DISTRIBUTION_MANAGER 19-11-2013 5.01.41 AM 328 (0x0148)
Successfully updated the package server status for ["Display=\\CMLABWIN71.CMLAB.COM\"]MSWNET:["SMS_SITE=PR1"]\\CMLABWIN71.CMLAB.COM\ for package PR100006, Status 3 SMS_DISTRIBUTION_MANAGER 19-11-2013 5.01.41 AM 328 (0x0148)
STATMSG: ID=2330 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=CMLABPR1.CMLAB.COM SITE=PR1 PID=4676 TID=328 GMTDATE=Tue Nov 19 13:01:41.576 2013 ISTR0="PR100006" ISTR1="["Display=\\CMLABWIN71.CMLAB.COM\"]MSWNET:["SMS_SITE=PR1"]\\CMLABWIN71.CMLAB.COM\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="PR100006" AID1=404 AVAL1="["Display=\\CMLABWIN71.CMLAB.COM\"]MSWNET:["SMS_SITE=PR1"]\\CMLABWIN71.CMLAB.COM\" SMS_DISTRIBUTION_MANAGER 19-11-2013 5.01.41 AM 328 (0x0148)
StateTable::CState::Handle - (2330:1 2013-11-19 13:01:41.576+00:00) >> (2331:1 2013-11-18 12:49:08.559+00:00) SMS_DISTRIBUTION_MANAGER 19-11-2013 5.01.41 AM 328 (0x0148)
CStateMsgReporter::DeliverMessages - Queued message: TT=1401 TIDT=0 TID='7F6041B0-3EE2-427F-AB72-B89610A6331C' SID=2330 MUF=0 PCNT=2, P1='PR1' P2='2013-11-19 13:01:41.576+00:00' P3='' P4='' P5='' SMS_DISTRIBUTION_MANAGER 19-11-2013 5.01.41 AM 328 (0x0148)
CStateMsgReporter::DeliverMessages - Created state message file: C:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\pz2r16zj.SMX SMS_DISTRIBUTION_MANAGER 19-11-2013 5.01.41 AM 328 (0x0148)
Successfully send state change notification 7F6041B0-3EE2-427F-AB72-B89610A6331C SMS_DISTRIBUTION_MANAGER 19-11-2013 5.01.41 AM 328 (0x0148)
Successfully delete package status file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\FXIYWOCM.STA SMS_DISTRIBUTION_MANAGER 19-11-2013 5.01.41 AM 328 (0x0148)

Hope this helps

Sudheesh Narayanaswamy

Support Escalation Engineer

Les filtres WMI sont très utilisés afin d'évaluer si un objet stratégie de groupe (GPO) s'applique sur un ordinateur. Les filtres les plus utilisés chez les clients permettent de déterminer entre autres :

• La version de Windows installée sur l'ordinateur.

• Le type de PC (Portable/Poste fixe).

• Le modèle/marque du PC.

Cependant, l'utilisation de filtres WMI sur les GPO va impacter les performances au démarrage. En effet, l'ordinateur doit évaluer si le filtre est vrai ou faux. En fonction du contenu de la requête WQL, l'évaluation du filtre prend plus de temps, ce qui retarde le processus d'application des GPOs.

Aussi l'utilisation d'un filtre WMI sur une GPO retarde l'application des GPO. En effet, si un filtre doit être évalué, le service Client Stratégie de groupe doit attendre que le service WinMgmt démarre et initialise la couche WMI. Une fois que la couche WMI est initialisée, un processus WMIPrvSe est créé et la requête est évaluée. En fonction des performances de la machine ou de l'état duRepository WMI, le temps d'attente avant l'exécution même de la requête WMI peut être plus ou moins long.

Bonnes pratiques

Eviter les requêtes WQL génériques

Pour une raison de simplicité, les exemples de filtres WMI utilisent tous des requêtes génériques de type SELECT * FROM Classe_WMI WHERE Condition.

Cependant, il est quand même plus long de récupérer tous les éléments de la classe WMI qu'un seul élément et ceci dégrade les performances. Pour optimiser votre filtre, il faut sélectionner qu'un seul élément au lieu d'utiliser le caractère générique *.

Voici un exemple pour déterminer si un PC est du type PC portable :

Select PCSystemType FROM Win32_ComputerSystem WHERE PCSystemType=2

Note: Plusieurs méthodes existent pour évaluer si une machine est un ordinateur portable, par exemple tester la présence du type de RAM So-Dimm.

D'autres type de requêtes sont à proscrire :

• Les requêtes utilisant l'opérateur LIKE

• Les requêtes utilisant la classe WMI Win32_Product (pour plus d'informations consultez l'article suivant : http://blogs.technet.com/b/askds/archive/2012/04/19/how-to-not-use-win32-product-in-group-policy-filtering.aspx

De nouvelles classes WMI ou attributs sont ajoutés à chaque nouvelle version d'un système d'exploitation Windows. Il faut alors vérifier que la requête fonctionne sur chaque système d'exploitation de votre infrastructure.

Pour filtrer les différentes versions de Windows Client on peut utiliser les requêtes suivantes :

Utilisation des Group Policy Préférences

Il est également possible de filtrer les Préférences avec le ciblage (Item-level targeting). L'item level Targeting utilise des API natives de Windows et n'utilise pas de WMI (sauf si la condition du ciblage est effectuée avec une requête WQL). Les performances de l'Item level targeting sont meilleures par rapport à un filtre WMI classique.

Si vous utilisez des Préférences, il est recommandé de choisir un ciblage avec l'item Level Targeting au lieu d'utiliser un filtre WMI sur l'objet GPO.

Pour plus d'informations vous pouvez consulter l'article suivant : http://technet.microsoft.com/en-us/library/cc733022.aspx

Correctifs pour améliorer les performances des composants WMI

Vous trouverez dans la KB suivante les correctifs de performances pour les composants WMI :

• Suggested hotfixes for WMI related issue on Windows platforms : http://support.microsoft.com/kb/2591403

• http://blogs.technet.com/b/askperf/archive/2011/08/05/suggested-hotfixes-for-wmi-related-issue-on-windows-platforms.aspx

Correctifs pour améliorer les performances des Group Policy Preferences

Windows 7 SP1

• Error code 0x80070003 when a Group Policy preference is applied to Windows 7 clients

•  http://support.microsoft.com/kb/2904034/en-US

• Long startup or logon time on a Windows 7-based or Windows Server 2008 R2-based client computer when you apply a Group Policy preference that has OU filtering

• http://support.microsoft.com/kb/2693010/en

• An enterprise hotfix rollup is available for Windows 7 SP1 and Windows Server 2008 R2 SP1

•  http://support.microsoft.com/kb/2775511/en-US

Summary: Kick off a formal WinSat evaluation on your computer running Windows 8.1.

 How can I use Windows PowerShell to run a formal WinSat evaluation on my computer running Windows 8.1?

 Open the Windows PowerShell console with Admin rights, and use the WinSat utility:

WinSat formal

Getting Smart recently created this awesome infographic on what schools need to implement blended learning. As the infographic describes, blended learning is more than electronic textbooks and productivity tools. It involves inventing and adopting new learning environments that work better for students and for teachers.

Do you need help with the tools needed for using the classroom to start blending your classroom? Go to http://www.microsoft.com/nz/windowsintheclassroom/ to learn about our complimentary Windows in the Classroom Seminars.

Hoje é Domingo, dia do nosso Final de Semana Surpresa.

Esta semana acompanhamos toda à movimentação da Comunidade TechNet Wiki Brasil e gostaria de compartilhar alguns destaques que mantém nosso Portal, um dos únicos Wiki exclusivos no TechNet, entre os recursos mais utilizados entre os profissionais de Tecnologia do Brasil e do mundo.

Para começar, vamos destacar alguns artigos publicados recentemente:

Artigos Interessantes

- Configuração do serviço de sincronização do Perfil Usuario "User Profile" no SharePoint por André Lage

- Windows Server 2012 R2 - Como configurar vários endereços IP em uma interface de rede por Marcelo Strippoli

- Recursos BizTalk Server no TechNet Wiki por Sandro Pereira

Vale lembrar que é muito importante utilizar sempre em seus artigos todas às tags referentes ao seu conteúdo, para facilitar e orientar à busca de informações pela Comunidade. Você pode saber mais sobre Boas Práticas de utilização de tags nos artigos TechNet Wiki: Tags de Tecnologia e Wiki: Tags Comuns. 

Desafio de Traduções do TechNet Wiki 2013

No Portal dos Wiki Ninjas - Internacional, o Desafio de Traduções está cada vez mais envolvente com nossa Comunidade entre os líderes. O mais importante neste Desafio é que podemos criar artigos, originados em Inglês ou outros idiomas e compartilhar este conhecimento na Comunidade Brasileira. Isto torna à integração das Informações e da Comunidade ainda maior, aproximando mais o autor do artigo, o tradutor e os profissionais que utilizam à informação.

Vale lembrar, sempre que traduzir um artigo de outro idioma para Português é necessário incluir à tag Translation into Portuguese. Você também pode divulgar ainda mais seu artigo criado em Português, traduzindo seu conteúdo para outro idioma que você conheça. Neste caso, após você traduzir seu artigo não esqueça de utilizar à tag Translated from Portuguese. 

Em ambos os casos, é extremamente importante citar o artigo original e, se existir, inclua também os links do mesmo artigo em outros idiomas, na seção "Outros Idiomas". Para maiores informações sobre como traduzir artigos, leia Wiki: Como traduzir TechNet Wiki artigos. Você pode querer traduzir um desses artigos citados acima para outro idioma, ou algum outro entre os grandes artigos de nossa Comunidade !

Encontre mais artigos em destaque para traduzir e ajude à Comunidade Brasileira crescer no Wiki Internacional. Todos nós temos à ganhar !

O Desafio vai até dia 12/01/2014, para participar basta traduzir ao menos um artigo. Leia mais sobre a participação de toda à Comunidade no Desafio de Traduções do TechNet Wiki 2013.

Até +,

Wiki Ninja Durval Ramos ( Twitter, Perfil )

원하지 않았지만, 여러 가지 이유로 서버를 Rebuild 해야 하는 일들이 생깁니다. 예를 들어 H/W 이슈로 서버를 재설치 해야 하는 일이 있는데, 아주 오래  전에 Exchange MBX서버 Mother Board가 나갔는데, H/W가 오래 되어서 교체를 못하고 새 서버에 설치해야 하는 일이 있었죠. 뿐만아니라 Exchange Service Pack 설치 작업에서 Crash가 생겨서 문제를 해결 할 수 없는 경우들도 종종 볼 수 있죠.

Exchange 2007의 경우는 setup.com /m:recovercms 옵션이 있었지만, Exchange 2007의 경우는 그런 옵션이 없습니다. 그래서 오늘은 DAG를 구성하고 있는 MBX 서버의 Rebuild 방법을 확인해 보도록 하겠습니다.

구성 환경

DAG로 내에는 MBX1과 MBX2 메일박스 서버가 구성되어 있고, MBXDB01에 대해 두 서버가 복제하고 있습니다. 이때 MBX02서버가 어떤 이유로 인해서 재구성이 팰요하다는 전제에서 다음 작업을 수행 합니다.

DAG Name: DAG

Node1: MBX01

Node2: MBX02

Database: MBXDB01

작업1: Database 복제 구성 정보 삭제

먼저 메일박스 서버를 재구성 하려면 복제 중인 Database Copy본을 제거해야 합니다.  서버를 Rebuild해야 하는 서버에 존재하는 Database Copy본을 다음 cmdlet을 이용하여 제거 합니다.

Remove-MailboxDatabaseCopy –Identity MBXDB01\MBX02

작업2: DAG로부터 메일박스 서버 제거

다음은 DAG에서 MBX02번을 멤버 서버에서 제거 시킵니다. 이때 주의할 사항은 반드시 -ConfigurationOnly 옵션을 사용해야 한다는 점입니다. 이 옵션을 빼게되면 해당 cmdlet은 다른 노드, 즉 MBX01서버에 연결하여 클러스터 서비스를 내리게 됩니다. 따라서 DAG는 전체가 망가지게 되겠죠?

Remove-DatabaseAvailabilityGroupServer –Identity DAG –MailboxServer MBX02  -ConfigurationOnly

작업3: 클러스터 서비스에서 구성 정보 삭제

DAG는 설치시에 Windows Failover Cluster 기능을 설치하지 않지만, DAG는 기본적으로 Windows Failover Cluster 를 사용합니다.  따라서 DAG에서 MBX02가 제거 되었다 하더라도, Cluser Node에서 MBX02를 제거해 주어야 합니다. 다음 클러스터 명령을 이용하여 MBX02를 DAG 클러스터에서 삭제합니다.

Cluster.exe DAG Node MBX02 /Evict

작업4: 서버 다시 구성

이제 MBX02를 재 구성하기 위한 준비가 되었습니다. 다음 두가지 경우가 있을 수 있습니다.
- 사용중인 MBX02를 Format후 다시 설치 합니다. 작업하기 전에 MBX02서버를 도메인에서 제거 하지 않고 바로 Format 후 OS 를 설치하고 서버 이름을 MBX02로 구성합니다. 
- 새로운 서버에 OS를 설치하고 기존 서버와 동일한 컴퓨터 이름(MBX02)으로 설정합니다.

작업5. AD에서 컴퓨터 계정 Reset

작업4에서 다시 구성된 컴퓨터를  MBX02라는 이름으로 도메인에 조인 하기 위해서는 AD에서 컴퓨터 계정을 Reset해야 합니다. Active Directory 사용자 및 컴퓨터를 열고 MBX02컴퓨터를 찾은 다음 마우스 오른쪽으로 누르고 Reset을 누릅니다.

그런 다음 MBX02서버를 AD에 Join 시키고 시스템을 다시 시작 합니다.

작업 6. Exchange 2010 Recover 설치

이제 서버를 Recover 합니다. 먼저 Exchange Server 2010을 설치하기 위해 필요한 Windows 구성 요소 및 요구사항이 만족되었는지 확인합니다. 조건이 만족 되었다면 다음 명령어로 Exchange Server 2010을 설치합니다.

setup.com /m:recoverserver

작업7. DAG에 MBX02 추가하기

Exchange 서버가 정상적으로 설치 되었습니다. 이제 DAG멤버 서버로 MBX02를 추가하면 Database 복제본을 다시 둘 수 있습니다.

Add-DatabaseAvailabilityGroupServer –Identity DAG –MailboxServer MBX02

이제 Database를 복제하기 위한 모든 준비가 끝났습니다. Database를 다시 복제 시킵니다.

2013 年 12 月の CU がリリースされましたのでお知らせします。

以下のリンクよりダウンロードできます。

SPS2013 の 12 月 CU は近日中にリリースされる予定です。公開されましたらこちらの記事を更新する予定です。

注意点

• SharePoint Server 2013 の CU 適用前には 2013 年 3 月の更新プログラムをインストールする必要があります。
• SharePoint Server 2010、SharePoint Foundation 2010 の 2013 年 12 月以降の CU 適用前には SP2をインストールする必要があります。
• SharePoint Server 2013 の CU には SharePoint Foundation 2013 の CU が含まれます。SharePoint Server 2013 with Project Server の CU には SharePoint Server 2013、SharePoint Foundation 2013 の CU が含まれます。いずれか 1 つの製品ファミリに対応した CU を適用すれば問題ありません。
• SharePoint Server 2010 の CU には SharePoint Foundation 2010 の CU が含まれます。SharePoint Server 2010 with Project Server の CU には SharePoint Server 2010、SharePoint Foundation 2010 の CU が含まれます。いずれか 1 つの製品ファミリに対応した CU を適用すれば問題ありません。
• インストールの完了後 SharePoint 製品構成ウィザードを実行する必要があります。

関連 KB

• KB 2849990 - SharePoint Foundation 2010
• KB 2849971 - SharePoint Server 2010
• KB 2849972 - Project Server 2010
• KB 2849961 - SharePoint Foundation 2013

• KB 2850013 - Office Web Apps Server 2013

入手先

• Download SharePoint Foundation 2010 2013-12 CU
• Download SharePoint Server 2010 2013-12 CU
• Download SharePoint Server 2010 with Project Server 2013-12 CU
• Download SharePoint Foundation 2013 2013-12 CU

• Download Office Web Apps Server 2013 2013-10 CU

関連サイト

• Update Center for Microsoft Office, Office Servers, and Related Products
• Updates for SharePoint Server 2010 and SharePoint Foundation 2010
• Updates for Project Server 2010
• SharePoint 2013 for IT pros
• Updates for Enterprise Search Products
• How to: install update packages on a SharePoint 2013 farm where search component and high availability search topologies are enabled
• Common Question: What is the difference between a PU, a CU and a COD?

I’ve written a few blog posts now that get into the deep technical details of Managed Availability. I hope you’ve liked them, and I’m not about to stop! However, I’ve gotten a lot of feedback that we also need some simpler overview articles. Fortunately, we’ve just completed documentation on TechNet with an overview of Managed Availability. This was written to address how the feature may be managed day-to-day.

Even that documentation doesn’t address how you respond when Managed Availability cannot resolve a problem on its own. This is the very most common interaction with Managed Availability, but we haven’t described how specifically to do so.

When Managed Availability is unable to recover the health of a server, it logs an event. Exchange Server has a long history of logging warning, error, and critical events into various channels when things go wrong. However, there are two things about Managed Availability events that make them more generally useful than our other error events:

• They all go to the same place on a server without any clutter
• They will only be logged when the standard recovery actions fail to restore health of the component

When one of these events is logged on any server in our datacenters, a member of the product group team responsible for that health set gets an immediate phone call.

No one likes to wake up at 2 AM to investigate and fix a problem with a server. This keeps us motivated to only have Managed Availability alerts for problems that really matter, and also to eliminate the cause of the alert by fixing underlying code bugs or automating the recovery. At the same time, there is nothing worse than finding out about incidents from customer calls to support. Every time that happens we have painful meetings about how we should have detected the condition first and woken someone up. These two conflicting forces strongly motivate the entire engineering team to keep these events accurate and useful.

The GUI

Along with a phone call, the on-call engineer receives an email with some information about the failure. The contents of this email are pulled from the event’s description.

The path in Event Viewer for these events is Microsoft-Exchange-ManagedAvailability/Monitoring. Error event 4 means that a health set has failed and gives the details of the monitor that has detected the failure. Information event 1 means that all monitors of a health set have become healthy.

The Exchange 2013 Management Pack for System Center Operations Manager nicely shows only the health sets that are currently failed instead of the Event Viewer’s method of displaying all health sets that have ever failed. SCOM will also roll up health sets into four primary health groups or three views.

The Shell

This wouldn’t be EHLO without some in-depth PowerShell scripts. The event viewer is nice and SCOM is great, but not everyone has SCOM. It would be pretty sweet to get the same behavior as SCOM to show only the health sets on a server that are currently failed.

Note: these logs serve a slightly different purpose than Get-HealthReport. Get-HealthReport shows the current health state of all of a server’s monitors. On the other hand, events are only logged in this channel once all the recovery actions for that monitor have been exhausted without fixing the problem. Also know that these events detail the failure. If you’re only going to take action based on one health metric, the events in this log is a better one. Get-HealthReport is still the best tool to show you the up-to-the-minute user experience.

We have a sample script that can help you with this; it is commented in a way that you can see what we were trying to accomplish. You can get the Get-ManagedAvailabilityAlerts.ps1 script here.

Either this method or Event Viewer will work pretty well for a handful of servers. If you have tens or hundreds of servers, we really recommend investing in SCOM or another robust and scalable event-collection system.

My other posts have dug deeply into troubleshooting difficult problems, and how Managed Availability gives an overwhelmingly immense amount of information about a server’s health. We rarely need to use these troubleshooting methods when running our datacenters. However, the only thing you need to resolve Exchange problems the way we do in Office 365 is a little bit of event viewer or scheduled script.

Abram Jackson
Program Manager, Exchange Server

Acting and voice coach MJ Vandivier teaches students at the Paramount Theatre in Austin, Texas, but when clients are far away, she turns to Skype to see and hear them in action to better help them.

Her experience is shared in the latest of the “Working Smarter, with Skype” series of videos, published on the Skype Workplace Blog.

Skype, Vandivier says, is “a terrific tool if I can’t be with somebody in person ... I have to be able to not just hear, but to see and to be able to read somebody …. Are they breathing well? Do they have the facial posture they need to, as far as voice? Are they being authentic as far as their acting? Skype allows me to travel in a way that I never could before, and benefit clients and also enrich my life by working with them.”

On the blog, Blake Shepard of Skype asks that if you have business experience, share your comments or upload your own video to YouTube, explaining how you use Skype in your business. Use the tag #skype4biz so that Skype can find you.

To read Shepard’s post, head over to the Skype Workplace Blog.

You might also be interested in:

• All aboard! Get on track with the Amtrak app, now on Windows Phone
• 4 ways Skype can help your business spread holiday cheer
• Five Skype features business users may not know about

Suzanne Choney
Microsoft News Center Staff

Today we’re publishing the December 2013 Security Bulletin Webcast Questions & Answers page.  We answered 17 questions in total, with the majority of questions focusing on the Graphics Component bulletin (MS13-096), Security Advisory 2915720 and Security Advisory 2905247.

We also wanted to note a new blog on the Microsoft Security Blog site on the top cyber threat predications for 2014. Topics from ransomware to regulation are covered by seven of Trustworthy Computing’s top thought leaders. If you don’t mind spoilers, take a few minutes to read what may be coming next.

We invite you to join us for the next scheduled webcast on Wednesday, January 15, 2013, at 11 a.m. PST (UTC -8), when we will go into detail about the January bulletin release and answer your bulletin deployment questions live on the air.

You can register to attend the webcast at the link below:

Date: Wednesday, January 15, 2013
Time: 11:00 a.m. PST (UTC -8)
Register: Attendee Registration

Have a safe and happy holiday season.
Thanks,

Dustin Childs
Group Manager, Response Communications
Microsoft Trustworthy Computing

Vergangene Woche wurde das SDK für den System Center 2012 R2 Configurtion Manager nachgereicht. Es enthält Dokumentation und Beispiele sowie umfangreiches Referenzmaterial zu den Schnittstellen im SCCM 2012 R2.

SCCM 2012 R2 SDK Beschreibung und Download

Ganz aktuell ist das Microsoft Assessment and Planning Toolkit in der Version 9.0 verfügbar. Die Neuerungen sind:

• Remote Desktop Services (RDS) Licensing Usage Tracking
• Software Inventur mit Software ID Tags (ISO 19770-2)
• SQL Server 2012 Usage Tracking mit User Access Logging (UAL)
• Unterstützung beim Auffinden von Systemen, die für die Server and Cloud Enrollment (SCE) Lizenzierung geeignet sind

MAP Toolkit 9.0 Homepage, Downloadseite und Direktdownload

Poor Max. He gets mad at his pesky little brother, who seems to love to break his toys among other things. Max wishes that “evil itself” could take his bro away, and sure enough – it does, much to Max’s dismay.

What Max does to try to un-do his wish come true is where the game’s fun begins, and you can watch the game’s announcement trailer above to get an idea of the journey and efforts Max must make in order to bring that annoying – but loved – little brother home.

To learn more, head over to Xbox Wire.

You might also be interested in:

• Solve a puzzle while facing an alien invasion and a volcano in “Girls Like Robots” on Windows Phone
• Use Xbox One SmartGlass app for “Ryse: Son of Rome” and you’ll find riches of your own
• “Countdown to 2014” daily deals for Xbox 360 starts Dec. 17

Suzanne Choney
Microsoft News Center Staff

Welcome to the Hot Sheet, a schedule of in-person training, live webcasts, and partner calls for Microsoft US partners. Courses are organized by role and by date, and this post is updated as needed to provide you with about a six-week outlook. Fewer live training opportunities around the holidays doesn't mean your learning has to take a back seat. Microsoft learning paths link you to on-demand courses that will help expand your Microsoft product knowledge and prepare for Microsoft exams and assessments. Use the learning plan feature to track your progress toward your goals.

To receive the Hot Sheet and other training and certification announcements in your inbox when they are published, enter your email address under Subscribe and follow on the main blog page. Courses offered by Microsoft Learning Partners are listed on Microsoft Tech Showcase.

Partner Calls

December 20 – SMB Partner Call for Central Region

December 20 – SMB Partner Call for West Region

January 10 – SMB Partner Call for East Region

January 15 – January 2014 Security Bulletin Webcast

January 17 – SMB Partner Call for Central Region

January 17 – SMB Partner Call for West Region

Sales Training

Technical Training

2014 Microsoft Events

January 29–30: Microsoft Dynamics AX | CRM Industry Summit

February 2–5: Microsoft Project Conference 2014

February 3–5: Microsoft Dynamics AX Technical Conference

February 18–20: Lync Conference 2014

March 3–6: Microsoft SharePoint Conference 2014

March 4 – 7: Microsoft Dynamics Convergence 2014

May 12–15: TechEd North America 2014

July 13–17: 2014 Worldwide Partner Conference