[mssms] RE: Failure on Request State Store
When I open the USMT drive I don't see that 1CBF4A1D$file:///\\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$ anywhere should I be able to see this directory? Pat Wilson CONFIDENTIALITY NOTICE: This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, dissemination, copying, printing, or other use of the e-mail by persons or entities other than the addressee is prohibited. If you have received this e-mail in error, please contact the sender or send an e-mail to the sender and immediately delete the material from your computer. Thank you. P Please consider the environment before printing this e-mail, and do so only if absolutely necessary From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: Friday, January 9, 2015 8:26 AM To: mssms@lists.myitforum.com Subject: [mssms] RE: Failure on Request State Store Error code 53 = The network path was not found. Thus, the client can't reach the SMP. This could be for one of many different reasons including (but not limited to) DNS resolution issues, firewalls, or a problem on the server. J From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Wilson, Patrick (Pat) Sent: Thursday, January 8, 2015 5:31 PM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] Failure on Request State Store Getting a Failure on Request State Store error Code 0x80004005. Doing a migration from XP to Windows 7. From SMSTS.LOG Adding \\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$file:///\\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$ to list OSDSMPClient1/8/2015 12:14:55 PM656 (0x0290) Failed to connect to \\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$file:///\\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$ (53).OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) Failed to connect to \\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$file:///\\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$ (53).OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) Cannot connect to http://LOKI.government.saltriver.pima-maricopa.nsn.us SMP root share OSDSMPClient1/8/2015 12:14:55 PM656 (0x0290) ClientRequestToSMP::DoRequest failed. error = (0x80004005). OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) Request to SMP 'http://LOKI.government.saltriver.pima-maricopa.nsn.us' failed with error (Code 0x80004005). Trying next SMP. OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) Failed to find an SMP that can serve request after trying 4 attempts. OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) ExecuteCaptureRequestSMP failed (0x80004005).OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) ExecuteCaptureRequest failed (0x80004005). OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) [Information_Technology_Logo] Pat Wilson SRPMIC Information Technology Desktop Services Senior Desktop Specialist CONFIDENTIALITY NOTICE: This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, dissemination, copying, printing, or other use of the e-mail by persons or entities other than the addressee is prohibited. If you have received this e-mail in error, please contact the sender or send an e-mail to the sender and immediately delete the material from your computer. Thank you. P Please consider the environment before printing this e-mail, and do so only if absolutely necessary.
[mssms] RE: Failure on Request State Store
Error code 53 = The network path was not found. Thus, the client can't reach the SMP. This could be for one of many different reasons including (but not limited to) DNS resolution issues, firewalls, or a problem on the server. J From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Wilson, Patrick (Pat) Sent: Thursday, January 8, 2015 5:31 PM To: mssms@lists.myitforum.com Subject: [mssms] Failure on Request State Store Getting a Failure on Request State Store error Code 0x80004005. Doing a migration from XP to Windows 7. From SMSTS.LOG Adding \\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$file:///\\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$ to list OSDSMPClient1/8/2015 12:14:55 PM656 (0x0290) Failed to connect to \\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$file:///\\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$ (53).OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) Failed to connect to \\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$file:///\\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$ (53).OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) Cannot connect to http://LOKI.government.saltriver.pima-maricopa.nsn.us SMP root share OSDSMPClient1/8/2015 12:14:55 PM656 (0x0290) ClientRequestToSMP::DoRequest failed. error = (0x80004005). OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) Request to SMP 'http://LOKI.government.saltriver.pima-maricopa.nsn.us' failed with error (Code 0x80004005). Trying next SMP. OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) Failed to find an SMP that can serve request after trying 4 attempts. OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) ExecuteCaptureRequestSMP failed (0x80004005).OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) ExecuteCaptureRequest failed (0x80004005). OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) [Information_Technology_Logo] Pat Wilson SRPMIC Information Technology Desktop Services Senior Desktop Specialist CONFIDENTIALITY NOTICE: This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, dissemination, copying, printing, or other use of the e-mail by persons or entities other than the addressee is prohibited. If you have received this e-mail in error, please contact the sender or send an e-mail to the sender and immediately delete the material from your computer. Thank you. P Please consider the environment before printing this e-mail, and do so only if absolutely necessary.
RE: [mssms] Upgrade (supersedence) user based deployment
Bump? From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Roland Janus Sent: Mittwoch, 7. Januar 2015 14:22 To: mssms@lists.myitforum.com Subject: [mssms] Upgrade (supersedence) user based deployment Not sure if I'm thinking about this right. I want all applications basically targeted to all users as available to shop. The user installs the application. Now a new version is created and superseded. If the deployment is available it would upgrade all clients where it is installed if the user is logged on. But what if I want all clients having the old version be upgraded, regardless if someone is logged on? Obviously required on all users isn't a choice. Can I only do that through device targeting (inventory with old version) or is there a choice to make this required for the users having this application? CM seems to know about those, but I have no idea if a user based collection can have the same data: The right number is users with application Can a user collection have that data? I didn't notice anything obvious in the query editor. -Roland
RE: [mssms] RE: Software Updates Maintenance Windows:
lol From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of James Avery Sent: Thursday, January 8, 2015 7:52 PM To: mssms@lists.myitforum.com Subject: RE: [mssms] RE: Software Updates Maintenance Windows: I told them we could do it. They came back and said they want to keep as it was the old way. I think it’s because they haven’t learned anything from me since they keep leaving their seat while I’m trying to train. From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: Thursday, January 08, 2015 4:17 PM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: RE: [mssms] RE: Software Updates Maintenance Windows: Correct. Still not sure what or how you would want it to change though? How is this not meeting your 5-6 window? J From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of James Avery Sent: Thursday, January 8, 2015 3:56 PM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: RE: [mssms] RE: Software Updates Maintenance Windows: Thanks guys. This tells me my thoughts about software update deployments are exactly like in 2007. So no changes in 2012 R2. Dog gone it. Thanks again, James From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Greg Thomas Sent: Thursday, January 08, 2015 12:41 PM To: Lutz, Ken Cc: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: RE: [mssms] RE: Software Updates Maintenance Windows: One other very important part that I forgot to list... If somebody is logged on the system getting patched, you also have to take into account the reboot countdown. If you have 90 minute reboot countdown in your client settings, your MW includes that in the reboot time (so your MW better be at least that long + time to run patches). If nobody is logged in, it will reboot right away. On Jan 8, 2015 12:32 PM, Lutz, Ken kl...@spokanecounty.orgmailto:kl...@spokanecounty.org wrote: Greg, Thanks for the reply. That is what I thought but I just wanted to verify. Thanks, Ken … From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Greg Thomas Sent: Thursday, January 08, 2015 8:38 AM To: Lutz, Ken Cc: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: Re: [mssms] RE: Software Updates Maintenance Windows: It should recalculate after every patch installed, to see if it has time to run the next one as well as reboot. In other words, if it gets through 7 of 10 patches and there are less than the max run time of the next patch (5 min by default) + reboot time (10 min I think) in the MW, then it will stop running any more patches in that window. On Jan 8, 2015 11:23 AM, Lutz, Ken kl...@spokanecounty.orgmailto:kl...@spokanecounty.org wrote: When updates total time is more than the length of the MW won’t it still try to install any updates that can get done in the MW time frame? Thanks, Ken … From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: Thursday, January 08, 2015 8:16 AM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Software Updates Maintenance Windows: Your requirement isn’t that they start at 5, it’s that they occur between 5 and 6 and that’s exactly what the MW does. So, based on that, your MW needs to be from 5-6 AM. I’m missing why that’s not acceptable though. With this MW in place, updates will start on online systems at 5 AM and no update will be installed that is expected to finish after the MW finishes. Note that the MW calculation also accounts for a final reboot (which I think it counts as 5, 10, or 15 minutes -- don’t remember which), thus it really won’t start any updates expected to finish after 5:45, 5;50, or 5:55 (depending upon the time it expects for the reboot). All updates by default are expected to take 5 minutes in ConfigMgr 2012 although this can be adjusted on an update by update basis. If there are lots of updates, it’s possible they all don’t fit into the window though. J From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of James Avery Sent: Thursday, January 8, 2015 9:05 AM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Software Updates Maintenance Windows: Has to be from 5-6am no time after due to other applications happening. 1. All systems request patches from the WSUS server 2. All systems have a local GPO (workgroup computers) to tell the system to install patches at 5am. 3. Some locations are 24hrs and must have a definite
[mssms] driver package mayhem
?TS was failing, tracked down to 7 driver packages with 0 bytes in size. Seen this before, thought you just updated dp's and off you go, no dice. So I have deleted all the driver packages, and the package folders (they were blank too) Re-creating a new driver pack for the hp 6005, wizard, says yes, package folder is empty. DriverCat log says, this driver has already been imported for each inf it finds. Stuck - what now, I'd delete the drivers (under drivers) but some are shared with other models that work. Is there a route forward, or ditch them all and start again... Stuart Watret Offshore - IT Ltd
[mssms] Site Backup Setup Mistake
We recently installed a new SCCM 2012 site and ran into an odd problem. When we set up the site backup in maintenance we simply chose a local drive letter for the destination. This was a bad mistake and so I wanted to warn others not to do the same thing. As it was pointed out to us by Microsoft support: “Local drive on site server for site data and database: Specifies that the backup files for the site and site database are stored in the specified path on the local disk drive of the site server. You must create the local folder before the backup task runs” From: http://technet.microsoft.com/en-us/library/gg712697.aspx#BKMK_BackupMaintenanceTask Section: “To Enable the site backup maintenance task” Since we missed that requirement, and found that smsbackup.exe creates a folder for itself (sitecodeBackup), we just assumed that backup folder on the root drive would be sufficient. What is not explained in the TechNet instruction is WHY one must create the local folder. The backup program will change that local folder's permissions when it creates the sitecodeBackup folder under it! Those changes remove rights for CREATOR OWNER and the local Users group and this was preventing access to the root of the drive we were using. Of course, we didn't know that smsbackup.exe was doing that, and it took some bit of security log auditing to find out how the permissions were getting changed and then more time to find out what we could do about it. I've asked Microsoft support to get the TechNet article updated to add an explanation to the instruction that security permissions will be set by the backup which I believe will reinforce the importance of creating that folder! The section states DRIVE and then throws that last bit in at the end, which I think makes it easy to miss. Anyway, I hope this will help other noobies setting up SCCM 2012. Russell Johnson
[mssms] RE: Failure on Request State Store
SMPSTOREs_1CBF4A1D$ is a share, not a folder. From memory, I think the folder that is shared is called the same thing though and will under the location specified in your SMP's configuration. If it's not there, that could probably cause a 53 also. Thus, you r SMP is broken in some way if it's not there. J From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Wilson, Patrick (Pat) Sent: Friday, January 9, 2015 10:13 AM To: mssms@lists.myitforum.com Subject: [mssms] RE: Failure on Request State Store When I open the USMT drive I don't see that 1CBF4A1D$file:///\\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$ anywhere should I be able to see this directory? Pat Wilson CONFIDENTIALITY NOTICE: This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, dissemination, copying, printing, or other use of the e-mail by persons or entities other than the addressee is prohibited. If you have received this e-mail in error, please contact the sender or send an e-mail to the sender and immediately delete the material from your computer. Thank you. P Please consider the environment before printing this e-mail, and do so only if absolutely necessary From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: Friday, January 9, 2015 8:26 AM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Failure on Request State Store Error code 53 = The network path was not found. Thus, the client can't reach the SMP. This could be for one of many different reasons including (but not limited to) DNS resolution issues, firewalls, or a problem on the server. J From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Wilson, Patrick (Pat) Sent: Thursday, January 8, 2015 5:31 PM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] Failure on Request State Store Getting a Failure on Request State Store error Code 0x80004005. Doing a migration from XP to Windows 7. From SMSTS.LOG Adding \\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$file:///\\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$ to list OSDSMPClient1/8/2015 12:14:55 PM656 (0x0290) Failed to connect to \\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$file:///\\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$ (53).OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) Failed to connect to \\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$file:///\\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$ (53).OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) Cannot connect to http://LOKI.government.saltriver.pima-maricopa.nsn.us SMP root share OSDSMPClient1/8/2015 12:14:55 PM656 (0x0290) ClientRequestToSMP::DoRequest failed. error = (0x80004005). OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) Request to SMP 'http://LOKI.government.saltriver.pima-maricopa.nsn.us' failed with error (Code 0x80004005). Trying next SMP. OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) Failed to find an SMP that can serve request after trying 4 attempts. OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) ExecuteCaptureRequestSMP failed (0x80004005).OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) ExecuteCaptureRequest failed (0x80004005). OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) [Information_Technology_Logo] Pat Wilson SRPMIC Information Technology Desktop Services Senior Desktop Specialist CONFIDENTIALITY NOTICE: This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, dissemination, copying, printing, or other use of the e-mail by persons or entities other than the addressee is prohibited. If you have received this e-mail in error, please contact the sender or send an e-mail to the sender and immediately delete the material from your computer. Thank you. P Please consider the environment before printing this e-mail, and do so only if absolutely necessary.
[mssms] RE: driver package mayhem
Could one of you do me a huge favor and file this on Connect? I’m compiling a
list of these sort of oddities into a bucket of things to potentially do in the
future to improve the product. ☺
Aaron
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Timothy Ransom
Sent: Friday, January 9, 2015 7:21 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: driver package mayhem
Here is an option from Microsoft support that I use.
In Driver package properties\Data Access:
Select Copy the content in this package to a package share on DPs.
Additional disk space is required on DPs if you select this option.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Stuart Watret
Sent: Friday, January 09, 2015 9:44 AM
To: mssms@lists.myitforum.com
Subject: [mssms] Re: driver package mayhem
so i did the trick of adding the blank text file to each directory in the
source folders, then reimported.
this has worked, and some kind soul wrote a batch file for the purpose, still
such an irritation, in what is a mature product.
thanks all
PUSHD %~dp0
@ECHO OFF
for /f tokens=* %%G IN ('dir /ad /b /s') DO (
echo. %%G\%~n0.txt
)
POPD
Stuart Watret
Offshore - IT Ltd
From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com
listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com on
behalf of Chris Carbone
chris.carb...@fairmountsantrol.commailto:chris.carb...@fairmountsantrol.com
Sent: 09 January 2015 14:15
To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com
Subject: [mssms] RE: driver package mayhem
I have also seen this numerous times. Usually what fixes this is if you add the
ini field under drivers and delete any duplicate ini names and THEN create a
driver package the 0 byte size issue goes away. Good luck, this can be an
aggravating problem.
From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com
[mailto:listsad...@lists.myitforum.com] On Behalf Of Stuart Watret
Sent: Friday, January 09, 2015 5:26 AM
To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com
Subject: [mssms] driver package mayhem
TS was failing, tracked down to 7 driver packages with 0 bytes in size.
Seen this before, thought you just updated dp's and off you go, no dice.
So I have deleted all the driver packages, and the package folders (they were
blank too)
Re-creating a new driver pack for the hp 6005, wizard, says yes, package folder
is empty.
DriverCat log says, this driver has already been imported for each inf it finds.
Stuck - what now, I'd delete the drivers (under drivers) but some are shared
with other models that work.
Is there a route forward, or ditch them all and start again...
Stuart Watret
Offshore - IT Ltd
This electronic mail transmission may contain confidential information intended
only for the use of the individual(s) identified as addressee(s). If you are
not the intended recipient, you are hereby notified that any disclosure,
copying, distribution or the taking of any action in reliance on the contents
of this electronic mail transmission is strictly prohibited. If you have
received this transmission in error, please notify me by telephone immediately.
**
GDOL CONFIDENTIALITY NOTICE: This transmission may contain confidential
information protected by state or federal law. The information is intended only
for use consistent with the state business discussed in this transmission. If
you are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution, or the taking of any action based on the
contents is strictly prohibited. If you have received this transmission in
error, please delete this email and notify the sender immediately. Your
cooperation is appreciated.
**
[mssms] RE: Changing SCCM port
That was my suggestion, but the complaint was that maintaining a QOS list of servers which may require changes in the future if servers get added/removed across all of the network devices would be too much work and likely would not be well implemented. Hence the desire to change the ports. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Matt Browne Sent: Friday, January 09, 2015 1:08 AM To: mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port We have looked at something similar in the past. If you are looking at just putting QoS on the download of updates etc, then it’s probably just BITS you need to be worried about (ie 80 443). There are many other ports that the client uses (ie RPC etc) but you probably don’t need to worry about those. We ended up creating a QoS rule for traffic to/from the main site servers and the DP’s, on those ports. Hope that helps From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Garth Jones Sent: 08 January 2015 23:49 To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port Err I would stay way from moving ports but…. Why can’t you Network team do QOS for BITS traffic? Their packetshaper should be able to do this without any problem. From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Atkinson, Matt T Sent: Thursday, January 8, 2015 6:24 PM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] Changing SCCM port Hi All, We’ve been asked to look in to what it would take to modify the current communication port used by our SCCM 2012 environment. Although I can see how to configure it from the beginning of a deployment, and where it can be changed, details online are sparse when it comes to changing the ports for an existing environment. My fear is that changing the communication port would leave our existing clients unmanaged and require us to redeploy the client. Anyone have any experience in doing this? The end goal is for our network team to be able to apply QOS policies for SCCM based simply on the port the traffic is happening on. The major concern being content downloads from clients to DPs. The options for BITS throttling leave a lot to be desired, hence the request for QOS policies to be used instead. Thanks! Matt This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. Information in this message is sent in confidence and is intended only for the use of the individual or entity to whom it is addressed. If you are not the intended recipient, any use, distribution or copying of the information is strictly forbidden. Please notify the sender immediately by return email or telephone 01823 721400. If you received this email in error please delete it and any copies of it from your system. Viridor Waste Management Limited Registered Office: Peninsula House, Rydon Lane, Exeter EX2 7HR Registered in England No. 575069 This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message.
[mssms] RE: driver package mayhem
Here is an option from Microsoft support that I use.
In Driver package properties\Data Access:
Select Copy the content in this package to a package share on DPs.
Additional disk space is required on DPs if you select this option.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Stuart Watret
Sent: Friday, January 09, 2015 9:44 AM
To: mssms@lists.myitforum.com
Subject: [mssms] Re: driver package mayhem
so i did the trick of adding the blank text file to each directory in the
source folders, then reimported.
this has worked, and some kind soul wrote a batch file for the purpose, still
such an irritation, in what is a mature product.
thanks all
PUSHD %~dp0
@ECHO OFF
for /f tokens=* %%G IN ('dir /ad /b /s') DO (
echo. %%G\%~n0.txt
)
POPD
Stuart Watret
Offshore - IT Ltd
From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com
listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com on
behalf of Chris Carbone
chris.carb...@fairmountsantrol.commailto:chris.carb...@fairmountsantrol.com
Sent: 09 January 2015 14:15
To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com
Subject: [mssms] RE: driver package mayhem
I have also seen this numerous times. Usually what fixes this is if you add the
ini field under drivers and delete any duplicate ini names and THEN create a
driver package the 0 byte size issue goes away. Good luck, this can be an
aggravating problem.
From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com
[mailto:listsad...@lists.myitforum.com] On Behalf Of Stuart Watret
Sent: Friday, January 09, 2015 5:26 AM
To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com
Subject: [mssms] driver package mayhem
TS was failing, tracked down to 7 driver packages with 0 bytes in size.
Seen this before, thought you just updated dp's and off you go, no dice.
So I have deleted all the driver packages, and the package folders (they were
blank too)
Re-creating a new driver pack for the hp 6005, wizard, says yes, package folder
is empty.
DriverCat log says, this driver has already been imported for each inf it finds.
Stuck - what now, I'd delete the drivers (under drivers) but some are shared
with other models that work.
Is there a route forward, or ditch them all and start again...
Stuart Watret
Offshore - IT Ltd
This electronic mail transmission may contain confidential information intended
only for the use of the individual(s) identified as addressee(s). If you are
not the intended recipient, you are hereby notified that any disclosure,
copying, distribution or the taking of any action in reliance on the contents
of this electronic mail transmission is strictly prohibited. If you have
received this transmission in error, please notify me by telephone immediately.
**
GDOL CONFIDENTIALITY NOTICE: This transmission may contain confidential
information protected by state or federal law. The information is intended
only for use consistent with the state business discussed in this transmission.
If you are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution, or the taking of any action based on the
contents is strictly prohibited. If you have received this transmission in
error, please delete this email and notify the sender immediately. Your
cooperation is appreciated.
**
[mssms] RE: Changing SCCM port
So instead of them keeping a QOS list you have to keep a port/application list? Makes perfect sense to me. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: Friday, January 09, 2015 2:57 PM To: mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port LOL From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Andreas Hammarskjöld Sent: Friday, January 9, 2015 12:38 PM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port Maybe they spent some time with the security people? ;-) From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: den 9 januari 2015 19:30 To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port Wow, that’s unusual, the network guys complaining about doing their job. I’ve never heard them do that before. J From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Atkinson, Matt T Sent: Friday, January 9, 2015 10:30 AM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port That was my suggestion, but the complaint was that maintaining a QOS list of servers which may require changes in the future if servers get added/removed across all of the network devices would be too much work and likely would not be well implemented. Hence the desire to change the ports. From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Matt Browne Sent: Friday, January 09, 2015 1:08 AM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port We have looked at something similar in the past. If you are looking at just putting QoS on the download of updates etc, then it’s probably just BITS you need to be worried about (ie 80 443). There are many other ports that the client uses (ie RPC etc) but you probably don’t need to worry about those. We ended up creating a QoS rule for traffic to/from the main site servers and the DP’s, on those ports. Hope that helps From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Garth Jones Sent: 08 January 2015 23:49 To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port Err I would stay way from moving ports but…. Why can’t you Network team do QOS for BITS traffic? Their packetshaper should be able to do this without any problem. From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Atkinson, Matt T Sent: Thursday, January 8, 2015 6:24 PM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] Changing SCCM port Hi All, We’ve been asked to look in to what it would take to modify the current communication port used by our SCCM 2012 environment. Although I can see how to configure it from the beginning of a deployment, and where it can be changed, details online are sparse when it comes to changing the ports for an existing environment. My fear is that changing the communication port would leave our existing clients unmanaged and require us to redeploy the client. Anyone have any experience in doing this? The end goal is for our network team to be able to apply QOS policies for SCCM based simply on the port the traffic is happening on. The major concern being content downloads from clients to DPs. The options for BITS throttling leave a lot to be desired, hence the request for QOS policies to be used instead. Thanks! Matt This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. Information in this message is sent in confidence and is intended only for the use of the individual or entity to whom it is addressed. If you are not the intended recipient, any use, distribution or copying of the information is strictly forbidden. Please notify the sender immediately by return email or telephone 01823 721400. If you received this email in error please delete it and any copies of it from your system. Viridor Waste Management Limited Registered Office: Peninsula House, Rydon Lane, Exeter EX2 7HR Registered
[mssms] RE: Changing SCCM port
What about using policy-based QoS on the DP to either set a hard limit on outbound bandwidth per port/subnet/application or mark the packets with a DSCP value? From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of David McSpadden Sent: Friday, January 09, 2015 2:04 PM To: 'mssms@lists.myitforum.com' Subject: [mssms] RE: Changing SCCM port So instead of them keeping a QOS list you have to keep a port/application list? Makes perfect sense to me. From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: Friday, January 09, 2015 2:57 PM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port LOL From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Andreas Hammarskjöld Sent: Friday, January 9, 2015 12:38 PM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port Maybe they spent some time with the security people? ;-) From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: den 9 januari 2015 19:30 To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port Wow, that’s unusual, the network guys complaining about doing their job. I’ve never heard them do that before. J From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Atkinson, Matt T Sent: Friday, January 9, 2015 10:30 AM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port That was my suggestion, but the complaint was that maintaining a QOS list of servers which may require changes in the future if servers get added/removed across all of the network devices would be too much work and likely would not be well implemented. Hence the desire to change the ports. From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Matt Browne Sent: Friday, January 09, 2015 1:08 AM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port We have looked at something similar in the past. If you are looking at just putting QoS on the download of updates etc, then it’s probably just BITS you need to be worried about (ie 80 443). There are many other ports that the client uses (ie RPC etc) but you probably don’t need to worry about those. We ended up creating a QoS rule for traffic to/from the main site servers and the DP’s, on those ports. Hope that helps From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Garth Jones Sent: 08 January 2015 23:49 To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port Err I would stay way from moving ports but…. Why can’t you Network team do QOS for BITS traffic? Their packetshaper should be able to do this without any problem. From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Atkinson, Matt T Sent: Thursday, January 8, 2015 6:24 PM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] Changing SCCM port Hi All, We’ve been asked to look in to what it would take to modify the current communication port used by our SCCM 2012 environment. Although I can see how to configure it from the beginning of a deployment, and where it can be changed, details online are sparse when it comes to changing the ports for an existing environment. My fear is that changing the communication port would leave our existing clients unmanaged and require us to redeploy the client. Anyone have any experience in doing this? The end goal is for our network team to be able to apply QOS policies for SCCM based simply on the port the traffic is happening on. The major concern being content downloads from clients to DPs. The options for BITS throttling leave a lot to be desired, hence the request for QOS policies to be used instead. Thanks! Matt This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. Information in this message is sent in confidence and is intended only for the use
[mssms] RE: driver package mayhem
Yarp = yes
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Aaron Czechowski
Sent: 09 January 2015 17:43
To: mssms@lists.myitforum.com
Subject: [mssms] RE: driver package mayhem
Could one of you do me a huge favor and file this on Connect? I’m compiling a
list of these sort of oddities into a bucket of things to potentially do in the
future to improve the product. ☺
Aaron
From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com
[mailto:listsad...@lists.myitforum.com] On Behalf Of Timothy Ransom
Sent: Friday, January 9, 2015 7:21 AM
To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com
Subject: [mssms] RE: driver package mayhem
Here is an option from Microsoft support that I use.
In Driver package properties\Data Access:
Select Copy the content in this package to a package share on DPs.
Additional disk space is required on DPs if you select this option.
From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com
[mailto:listsad...@lists.myitforum.com] On Behalf Of Stuart Watret
Sent: Friday, January 09, 2015 9:44 AM
To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com
Subject: [mssms] Re: driver package mayhem
so i did the trick of adding the blank text file to each directory in the
source folders, then reimported.
this has worked, and some kind soul wrote a batch file for the purpose, still
such an irritation, in what is a mature product.
thanks all
PUSHD %~dp0
@ECHO OFF
for /f tokens=* %%G IN ('dir /ad /b /s') DO (
echo. %%G\%~n0.txt
)
POPD
Stuart Watret
Offshore - IT Ltd
From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com
listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com on
behalf of Chris Carbone
chris.carb...@fairmountsantrol.commailto:chris.carb...@fairmountsantrol.com
Sent: 09 January 2015 14:15
To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com
Subject: [mssms] RE: driver package mayhem
I have also seen this numerous times. Usually what fixes this is if you add the
ini field under drivers and delete any duplicate ini names and THEN create a
driver package the 0 byte size issue goes away. Good luck, this can be an
aggravating problem.
From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com
[mailto:listsad...@lists.myitforum.com] On Behalf Of Stuart Watret
Sent: Friday, January 09, 2015 5:26 AM
To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com
Subject: [mssms] driver package mayhem
TS was failing, tracked down to 7 driver packages with 0 bytes in size.
Seen this before, thought you just updated dp's and off you go, no dice.
So I have deleted all the driver packages, and the package folders (they were
blank too)
Re-creating a new driver pack for the hp 6005, wizard, says yes, package folder
is empty.
DriverCat log says, this driver has already been imported for each inf it finds.
Stuck - what now, I'd delete the drivers (under drivers) but some are shared
with other models that work.
Is there a route forward, or ditch them all and start again...
Stuart Watret
Offshore - IT Ltd
This electronic mail transmission may contain confidential information intended
only for the use of the individual(s) identified as addressee(s). If you are
not the intended recipient, you are hereby notified that any disclosure,
copying, distribution or the taking of any action in reliance on the contents
of this electronic mail transmission is strictly prohibited. If you have
received this transmission in error, please notify me by telephone immediately.
**
GDOL CONFIDENTIALITY NOTICE: This transmission may contain confidential
information protected by state or federal law. The information is intended only
for use consistent with the state business discussed in this transmission. If
you are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution, or the taking of any action based on the
contents is strictly prohibited. If you have received this transmission in
error, please delete this email and notify the sender immediately. Your
cooperation is appreciated.
**
[mssms] RE: Changing SCCM port
Thanks Doug, someone from our network group had mentioned that you can tag traffic coming from a particular machine with a specific identifier to single it out (I can see the “It’s called an IP” jokes now). DSCP must have been what they were talking about, but I was not familiar with that until now. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Doug Barrett Sent: Friday, January 09, 2015 1:40 PM To: mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port What about using policy-based QoS on the DP to either set a hard limit on outbound bandwidth per port/subnet/application or mark the packets with a DSCP value? From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of David McSpadden Sent: Friday, January 09, 2015 2:04 PM To: 'mssms@lists.myitforum.com' Subject: [mssms] RE: Changing SCCM port So instead of them keeping a QOS list you have to keep a port/application list? Makes perfect sense to me. From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: Friday, January 09, 2015 2:57 PM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port LOL From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Andreas Hammarskjöld Sent: Friday, January 9, 2015 12:38 PM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port Maybe they spent some time with the security people? ;-) From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: den 9 januari 2015 19:30 To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port Wow, that’s unusual, the network guys complaining about doing their job. I’ve never heard them do that before. J From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Atkinson, Matt T Sent: Friday, January 9, 2015 10:30 AM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port That was my suggestion, but the complaint was that maintaining a QOS list of servers which may require changes in the future if servers get added/removed across all of the network devices would be too much work and likely would not be well implemented. Hence the desire to change the ports. From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Matt Browne Sent: Friday, January 09, 2015 1:08 AM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port We have looked at something similar in the past. If you are looking at just putting QoS on the download of updates etc, then it’s probably just BITS you need to be worried about (ie 80 443). There are many other ports that the client uses (ie RPC etc) but you probably don’t need to worry about those. We ended up creating a QoS rule for traffic to/from the main site servers and the DP’s, on those ports. Hope that helps From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Garth Jones Sent: 08 January 2015 23:49 To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port Err I would stay way from moving ports but…. Why can’t you Network team do QOS for BITS traffic? Their packetshaper should be able to do this without any problem. From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Atkinson, Matt T Sent: Thursday, January 8, 2015 6:24 PM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] Changing SCCM port Hi All, We’ve been asked to look in to what it would take to modify the current communication port used by our SCCM 2012 environment. Although I can see how to configure it from the beginning of a deployment, and where it can be changed, details online are sparse when it comes to changing the ports for an existing environment. My fear is that changing the communication port would leave our existing clients unmanaged and require us to redeploy the client. Anyone have any experience in doing this? The end goal is for our network team to be able to apply QOS policies for SCCM based simply on the port the traffic is happening on. The major concern being content downloads from clients to DPs. The options for BITS throttling leave a lot to be desired, hence the request for QOS policies to be used instead. Thanks! Matt This message is intended for the
RE: [mssms] Site Backup Setup Mistake
Another reason to use a native SQL backup and not mess with the built-in maintenance task. J From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of RJ Subscriber Sent: Friday, January 9, 2015 11:11 AM To: mssms@lists.myITforum.com Subject: [mssms] Site Backup Setup Mistake We recently installed a new SCCM 2012 site and ran into an odd problem. When we set up the site backup in maintenance we simply chose a local drive letter for the destination. This was a bad mistake and so I wanted to warn others not to do the same thing. As it was pointed out to us by Microsoft support: Local drive on site server for site data and database: Specifies that the backup files for the site and site database are stored in the specified path on the local disk drive of the site server. You must create the local folder before the backup task runs From: http://technet.microsoft.com/en-us/library/gg712697.aspx#BKMK_BackupMaintenanceTask Section: To Enable the site backup maintenance task Since we missed that requirement, and found that smsbackup.exe creates a folder for itself (sitecodeBackup), we just assumed that backup folder on the root drive would be sufficient. What is not explained in the TechNet instruction is WHY one must create the local folder. The backup program will change that local folder's permissions when it creates the sitecodeBackup folder under it! Those changes remove rights for CREATOR OWNER and the local Users group and this was preventing access to the root of the drive we were using. Of course, we didn't know that smsbackup.exe was doing that, and it took some bit of security log auditing to find out how the permissions were getting changed and then more time to find out what we could do about it. I've asked Microsoft support to get the TechNet article updated to add an explanation to the instruction that security permissions will be set by the backup which I believe will reinforce the importance of creating that folder! The section states DRIVE and then throws that last bit in at the end, which I think makes it easy to miss. Anyway, I hope this will help other noobies setting up SCCM 2012. Russell Johnson
[mssms] RE: Changing SCCM port
Wow, that’s unusual, the network guys complaining about doing their job. I’ve never heard them do that before. J From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Atkinson, Matt T Sent: Friday, January 9, 2015 10:30 AM To: mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port That was my suggestion, but the complaint was that maintaining a QOS list of servers which may require changes in the future if servers get added/removed across all of the network devices would be too much work and likely would not be well implemented. Hence the desire to change the ports. From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Matt Browne Sent: Friday, January 09, 2015 1:08 AM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port We have looked at something similar in the past. If you are looking at just putting QoS on the download of updates etc, then it’s probably just BITS you need to be worried about (ie 80 443). There are many other ports that the client uses (ie RPC etc) but you probably don’t need to worry about those. We ended up creating a QoS rule for traffic to/from the main site servers and the DP’s, on those ports. Hope that helps From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Garth Jones Sent: 08 January 2015 23:49 To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port Err I would stay way from moving ports but…. Why can’t you Network team do QOS for BITS traffic? Their packetshaper should be able to do this without any problem. From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Atkinson, Matt T Sent: Thursday, January 8, 2015 6:24 PM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] Changing SCCM port Hi All, We’ve been asked to look in to what it would take to modify the current communication port used by our SCCM 2012 environment. Although I can see how to configure it from the beginning of a deployment, and where it can be changed, details online are sparse when it comes to changing the ports for an existing environment. My fear is that changing the communication port would leave our existing clients unmanaged and require us to redeploy the client. Anyone have any experience in doing this? The end goal is for our network team to be able to apply QOS policies for SCCM based simply on the port the traffic is happening on. The major concern being content downloads from clients to DPs. The options for BITS throttling leave a lot to be desired, hence the request for QOS policies to be used instead. Thanks! Matt This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. Information in this message is sent in confidence and is intended only for the use of the individual or entity to whom it is addressed. If you are not the intended recipient, any use, distribution or copying of the information is strictly forbidden. Please notify the sender immediately by return email or telephone 01823 721400. If you received this email in error please delete it and any copies of it from your system. Viridor Waste Management Limited Registered Office: Peninsula House, Rydon Lane, Exeter EX2 7HR Registered in England No. 575069 This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message.
[mssms] RE: Changing SCCM port
Maybe they spent some time with the security people? ;-) From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: den 9 januari 2015 19:30 To: mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port Wow, that’s unusual, the network guys complaining about doing their job. I’ve never heard them do that before. J From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Atkinson, Matt T Sent: Friday, January 9, 2015 10:30 AM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port That was my suggestion, but the complaint was that maintaining a QOS list of servers which may require changes in the future if servers get added/removed across all of the network devices would be too much work and likely would not be well implemented. Hence the desire to change the ports. From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Matt Browne Sent: Friday, January 09, 2015 1:08 AM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port We have looked at something similar in the past. If you are looking at just putting QoS on the download of updates etc, then it’s probably just BITS you need to be worried about (ie 80 443). There are many other ports that the client uses (ie RPC etc) but you probably don’t need to worry about those. We ended up creating a QoS rule for traffic to/from the main site servers and the DP’s, on those ports. Hope that helps From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Garth Jones Sent: 08 January 2015 23:49 To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port Err I would stay way from moving ports but…. Why can’t you Network team do QOS for BITS traffic? Their packetshaper should be able to do this without any problem. From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Atkinson, Matt T Sent: Thursday, January 8, 2015 6:24 PM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] Changing SCCM port Hi All, We’ve been asked to look in to what it would take to modify the current communication port used by our SCCM 2012 environment. Although I can see how to configure it from the beginning of a deployment, and where it can be changed, details online are sparse when it comes to changing the ports for an existing environment. My fear is that changing the communication port would leave our existing clients unmanaged and require us to redeploy the client. Anyone have any experience in doing this? The end goal is for our network team to be able to apply QOS policies for SCCM based simply on the port the traffic is happening on. The major concern being content downloads from clients to DPs. The options for BITS throttling leave a lot to be desired, hence the request for QOS policies to be used instead. Thanks! Matt This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. Information in this message is sent in confidence and is intended only for the use of the individual or entity to whom it is addressed. If you are not the intended recipient, any use, distribution or copying of the information is strictly forbidden. Please notify the sender immediately by return email or telephone 01823 721400. If you received this email in error please delete it and any copies of it from your system. Viridor Waste Management Limited Registered Office: Peninsula House, Rydon Lane, Exeter EX2 7HR Registered in England No. 575069 This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message.
[mssms] RE: Changing SCCM port
LOL From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Andreas Hammarskjöld Sent: Friday, January 9, 2015 12:38 PM To: mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port Maybe they spent some time with the security people? ;-) From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: den 9 januari 2015 19:30 To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port Wow, that’s unusual, the network guys complaining about doing their job. I’ve never heard them do that before. J From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Atkinson, Matt T Sent: Friday, January 9, 2015 10:30 AM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port That was my suggestion, but the complaint was that maintaining a QOS list of servers which may require changes in the future if servers get added/removed across all of the network devices would be too much work and likely would not be well implemented. Hence the desire to change the ports. From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Matt Browne Sent: Friday, January 09, 2015 1:08 AM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port We have looked at something similar in the past. If you are looking at just putting QoS on the download of updates etc, then it’s probably just BITS you need to be worried about (ie 80 443). There are many other ports that the client uses (ie RPC etc) but you probably don’t need to worry about those. We ended up creating a QoS rule for traffic to/from the main site servers and the DP’s, on those ports. Hope that helps From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Garth Jones Sent: 08 January 2015 23:49 To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port Err I would stay way from moving ports but…. Why can’t you Network team do QOS for BITS traffic? Their packetshaper should be able to do this without any problem. From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Atkinson, Matt T Sent: Thursday, January 8, 2015 6:24 PM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] Changing SCCM port Hi All, We’ve been asked to look in to what it would take to modify the current communication port used by our SCCM 2012 environment. Although I can see how to configure it from the beginning of a deployment, and where it can be changed, details online are sparse when it comes to changing the ports for an existing environment. My fear is that changing the communication port would leave our existing clients unmanaged and require us to redeploy the client. Anyone have any experience in doing this? The end goal is for our network team to be able to apply QOS policies for SCCM based simply on the port the traffic is happening on. The major concern being content downloads from clients to DPs. The options for BITS throttling leave a lot to be desired, hence the request for QOS policies to be used instead. Thanks! Matt This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. Information in this message is sent in confidence and is intended only for the use of the individual or entity to whom it is addressed. If you are not the intended recipient, any use, distribution or copying of the information is strictly forbidden. Please notify the sender immediately by return email or telephone 01823 721400. If you received this email in error please delete it and any copies of it from your system. Viridor Waste Management Limited Registered Office: Peninsula House, Rydon Lane, Exeter EX2 7HR Registered in England No. 575069 This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message
[mssms] RE: driver package mayhem
https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/1082184
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Aaron Czechowski
Sent: 09 January 2015 17:43
To: mssms@lists.myitforum.com
Subject: [mssms] RE: driver package mayhem
Could one of you do me a huge favor and file this on Connect? I’m compiling a
list of these sort of oddities into a bucket of things to potentially do in the
future to improve the product. ☺
Aaron
From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com
[mailto:listsad...@lists.myitforum.com] On Behalf Of Timothy Ransom
Sent: Friday, January 9, 2015 7:21 AM
To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com
Subject: [mssms] RE: driver package mayhem
Here is an option from Microsoft support that I use.
In Driver package properties\Data Access:
Select Copy the content in this package to a package share on DPs.
Additional disk space is required on DPs if you select this option.
From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com
[mailto:listsad...@lists.myitforum.com] On Behalf Of Stuart Watret
Sent: Friday, January 09, 2015 9:44 AM
To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com
Subject: [mssms] Re: driver package mayhem
so i did the trick of adding the blank text file to each directory in the
source folders, then reimported.
this has worked, and some kind soul wrote a batch file for the purpose, still
such an irritation, in what is a mature product.
thanks all
PUSHD %~dp0
@ECHO OFF
for /f tokens=* %%G IN ('dir /ad /b /s') DO (
echo. %%G\%~n0.txt
)
POPD
Stuart Watret
Offshore - IT Ltd
From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com
listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com on
behalf of Chris Carbone
chris.carb...@fairmountsantrol.commailto:chris.carb...@fairmountsantrol.com
Sent: 09 January 2015 14:15
To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com
Subject: [mssms] RE: driver package mayhem
I have also seen this numerous times. Usually what fixes this is if you add the
ini field under drivers and delete any duplicate ini names and THEN create a
driver package the 0 byte size issue goes away. Good luck, this can be an
aggravating problem.
From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com
[mailto:listsad...@lists.myitforum.com] On Behalf Of Stuart Watret
Sent: Friday, January 09, 2015 5:26 AM
To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com
Subject: [mssms] driver package mayhem
TS was failing, tracked down to 7 driver packages with 0 bytes in size.
Seen this before, thought you just updated dp's and off you go, no dice.
So I have deleted all the driver packages, and the package folders (they were
blank too)
Re-creating a new driver pack for the hp 6005, wizard, says yes, package folder
is empty.
DriverCat log says, this driver has already been imported for each inf it finds.
Stuck - what now, I'd delete the drivers (under drivers) but some are shared
with other models that work.
Is there a route forward, or ditch them all and start again...
Stuart Watret
Offshore - IT Ltd
This electronic mail transmission may contain confidential information intended
only for the use of the individual(s) identified as addressee(s). If you are
not the intended recipient, you are hereby notified that any disclosure,
copying, distribution or the taking of any action in reliance on the contents
of this electronic mail transmission is strictly prohibited. If you have
received this transmission in error, please notify me by telephone immediately.
**
GDOL CONFIDENTIALITY NOTICE: This transmission may contain confidential
information protected by state or federal law. The information is intended only
for use consistent with the state business discussed in this transmission. If
you are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution, or the taking of any action based on the
contents is strictly prohibited. If you have received this transmission in
error, please delete this email and notify the sender immediately. Your
cooperation is appreciated.
**
[mssms] RE: Failure on Request State Store
Should I remove the role and re-add it? Pat Wilson CONFIDENTIALITY NOTICE: This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, dissemination, copying, printing, or other use of the e-mail by persons or entities other than the addressee is prohibited. If you have received this e-mail in error, please contact the sender or send an e-mail to the sender and immediately delete the material from your computer. Thank you. P Please consider the environment before printing this e-mail, and do so only if absolutely necessary From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: Friday, January 9, 2015 11:33 AM To: mssms@lists.myitforum.com Subject: [mssms] RE: Failure on Request State Store SMPSTOREs_1CBF4A1D$ is a share, not a folder. From memory, I think the folder that is shared is called the same thing though and will under the location specified in your SMP's configuration. If it's not there, that could probably cause a 53 also. Thus, you r SMP is broken in some way if it's not there. J From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Wilson, Patrick (Pat) Sent: Friday, January 9, 2015 10:13 AM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Failure on Request State Store When I open the USMT drive I don't see that 1CBF4A1D$file:///\\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$ anywhere should I be able to see this directory? Pat Wilson CONFIDENTIALITY NOTICE: This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, dissemination, copying, printing, or other use of the e-mail by persons or entities other than the addressee is prohibited. If you have received this e-mail in error, please contact the sender or send an e-mail to the sender and immediately delete the material from your computer. Thank you. P Please consider the environment before printing this e-mail, and do so only if absolutely necessary From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: Friday, January 9, 2015 8:26 AM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Failure on Request State Store Error code 53 = The network path was not found. Thus, the client can't reach the SMP. This could be for one of many different reasons including (but not limited to) DNS resolution issues, firewalls, or a problem on the server. J From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Wilson, Patrick (Pat) Sent: Thursday, January 8, 2015 5:31 PM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] Failure on Request State Store Getting a Failure on Request State Store error Code 0x80004005. Doing a migration from XP to Windows 7. From SMSTS.LOG Adding \\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$file:///\\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$ to list OSDSMPClient1/8/2015 12:14:55 PM656 (0x0290) Failed to connect to \\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$file:///\\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$ (53).OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) Failed to connect to \\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$file:///\\LOKI.government.saltriver.pima-maricopa.nsn.us\SMPSTOREs_1CBF4A1D$ (53).OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) Cannot connect to http://LOKI.government.saltriver.pima-maricopa.nsn.us SMP root share OSDSMPClient1/8/2015 12:14:55 PM656 (0x0290) ClientRequestToSMP::DoRequest failed. error = (0x80004005). OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) Request to SMP 'http://LOKI.government.saltriver.pima-maricopa.nsn.us' failed with error (Code 0x80004005). Trying next SMP. OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) Failed to find an SMP that can serve request after trying 4 attempts. OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) ExecuteCaptureRequestSMP failed (0x80004005).OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) ExecuteCaptureRequest failed (0x80004005). OSDSMPClient 1/8/2015 12:14:55 PM656 (0x0290) [Information_Technology_Logo] Pat Wilson SRPMIC Information Technology Desktop Services Senior Desktop Specialist CONFIDENTIALITY NOTICE: This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged
[mssms] RE: Changing SCCM port
We have looked at something similar in the past. If you are looking at just putting QoS on the download of updates etc, then it's probably just BITS you need to be worried about (ie 80 443). There are many other ports that the client uses (ie RPC etc) but you probably don't need to worry about those. We ended up creating a QoS rule for traffic to/from the main site servers and the DP's, on those ports. Hope that helps From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Garth Jones Sent: 08 January 2015 23:49 To: mssms@lists.myitforum.com Subject: [mssms] RE: Changing SCCM port Err I would stay way from moving ports but Why can't you Network team do QOS for BITS traffic? Their packetshaper should be able to do this without any problem. From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Atkinson, Matt T Sent: Thursday, January 8, 2015 6:24 PM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] Changing SCCM port Hi All, We've been asked to look in to what it would take to modify the current communication port used by our SCCM 2012 environment. Although I can see how to configure it from the beginning of a deployment, and where it can be changed, details online are sparse when it comes to changing the ports for an existing environment. My fear is that changing the communication port would leave our existing clients unmanaged and require us to redeploy the client. Anyone have any experience in doing this? The end goal is for our network team to be able to apply QOS policies for SCCM based simply on the port the traffic is happening on. The major concern being content downloads from clients to DPs. The options for BITS throttling leave a lot to be desired, hence the request for QOS policies to be used instead. Thanks! Matt This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. --- Information in this message is sent in confidence and is intended only for the use of the individual or entity to whom it is addressed. If you are not the intended recipient, any use, distribution or copying of the information is strictly forbidden. Please notify the sender immediately by return email or telephone 01823 721400. If you received this email in error please delete it and any copies of it from your system. Viridor Waste Management Limited Registered Office: Peninsula House, Rydon Lane, Exeter EX2 7HR Registered in England No. 575069 ---
Re: [mssms] driver package mayhem
Spot check some of your drivers and look at the properties (or powershell them all out if you are comfortable with that). You should see the content source path in the properties. I'd be willing to bet those drivers are no longer at that path. The reason they work with some packages is because those packages have not been updated since the original driver source was moved or deleted. On Jan 9, 2015 5:25 AM, Stuart Watret stu...@offshore-it.co.uk wrote: TS was failing, tracked down to 7 driver packages with 0 bytes in size. Seen this before, thought you just updated dps and off you go, no dice. So I have deleted all the driver packages, and the package folders (they were blank too) Re-creating a new driver pack for the hp 6005, wizard, says yes, package folder is empty. DriverCat log says, this driver has already been imported for each inf it finds. Stuck - what now, Id delete the drivers (under drivers) but some are shared with other models that work. Is there a route forward, or ditch them all and start again... Stuart Watret Offshore - IT Ltd
RE: [mssms] Query for needed updates
I think Garth's free reports have this. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Mario Van Uytsel Sent: Friday, January 09, 2015 7:59 AM To: mssms@lists.myitforum.com Subject: [mssms] Query for needed updates Hello all, Can someone help me to get a query/report that will give me the amount of windows updates that still need to be installed on the devices that belong to a certain collection. Ex: Server14 updates Server225 updates ... Where server 1 and 2 are in collection 1 Thanks Mario Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
[mssms] SCCM 2012 Detection Method issue
Hello, We have recently upgraded our Bomgar client and pushed it out via SCCM. All is going well except I'm finding that only using the MSI product code for the detection method does not seem to always work properly. I'm finding that some clients are finding this MSI code and not running the install. So I wanted to add another detection method. What I would like to do is the following... I want to have this key as a detection method, the only problem is the path in registry to this key is dynamic. If you look below, that last part 141815881 is a different number for each client. Is there a way I could put a wildcard in to not look at that part? HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Bomgar Jump Client [support.fairmountminerals.com-1418158881] The DisplayVersion key (14.3.1) is what I will use if I can get the above part figured out. [cid:image001.jpg@01D02BEC.1A9BAAB0] Thanks in advance! This electronic mail transmission may contain confidential information intended only for the use of the individual(s) identified as addressee(s). If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this electronic mail transmission is strictly prohibited. If you have received this transmission in error, please notify me by telephone immediately.
[mssms] RE: driver package mayhem
I have also seen this numerous times. Usually what fixes this is if you add the ini field under drivers and delete any duplicate ini names and THEN create a driver package the 0 byte size issue goes away. Good luck, this can be an aggravating problem. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Stuart Watret Sent: Friday, January 09, 2015 5:26 AM To: mssms@lists.myitforum.com Subject: [mssms] driver package mayhem TS was failing, tracked down to 7 driver packages with 0 bytes in size. Seen this before, thought you just updated dp's and off you go, no dice. So I have deleted all the driver packages, and the package folders (they were blank too) Re-creating a new driver pack for the hp 6005, wizard, says yes, package folder is empty. DriverCat log says, this driver has already been imported for each inf it finds. Stuck - what now, I'd delete the drivers (under drivers) but some are shared with other models that work. Is there a route forward, or ditch them all and start again... Stuart Watret Offshore - IT Ltd This electronic mail transmission may contain confidential information intended only for the use of the individual(s) identified as addressee(s). If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this electronic mail transmission is strictly prohibited. If you have received this transmission in error, please notify me by telephone immediately.
[mssms] Query for needed updates
Hello all, Can someone help me to get a query/report that will give me the amount of windows updates that still need to be installed on the devices that belong to a certain collection. Ex: Server14 updates Server225 updates ... Where server 1 and 2 are in collection 1 Thanks Mario
RE: [mssms] RE: Software Updates Maintenance Windows:
There's also a reboot turnaround time that is added in there. I can't recall how many minutes it is. This is non-configurable. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Greg Thomas Sent: Thursday, January 08, 2015 12:41 PM To: Lutz, Ken Cc: mssms@lists.myitforum.com Subject: RE: [mssms] RE: Software Updates Maintenance Windows: One other very important part that I forgot to list... If somebody is logged on the system getting patched, you also have to take into account the reboot countdown. If you have 90 minute reboot countdown in your client settings, your MW includes that in the reboot time (so your MW better be at least that long + time to run patches). If nobody is logged in, it will reboot right away. On Jan 8, 2015 12:32 PM, Lutz, Ken kl...@spokanecounty.orgmailto:kl...@spokanecounty.org wrote: Greg, Thanks for the reply. That is what I thought but I just wanted to verify. Thanks, Ken … From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Greg Thomas Sent: Thursday, January 08, 2015 8:38 AM To: Lutz, Ken Cc: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: Re: [mssms] RE: Software Updates Maintenance Windows: It should recalculate after every patch installed, to see if it has time to run the next one as well as reboot. In other words, if it gets through 7 of 10 patches and there are less than the max run time of the next patch (5 min by default) + reboot time (10 min I think) in the MW, then it will stop running any more patches in that window. On Jan 8, 2015 11:23 AM, Lutz, Ken kl...@spokanecounty.orgmailto:kl...@spokanecounty.org wrote: When updates total time is more than the length of the MW won’t it still try to install any updates that can get done in the MW time frame? Thanks, Ken … From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: Thursday, January 08, 2015 8:16 AM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Software Updates Maintenance Windows: Your requirement isn’t that they start at 5, it’s that they occur between 5 and 6 and that’s exactly what the MW does. So, based on that, your MW needs to be from 5-6 AM. I’m missing why that’s not acceptable though. With this MW in place, updates will start on online systems at 5 AM and no update will be installed that is expected to finish after the MW finishes. Note that the MW calculation also accounts for a final reboot (which I think it counts as 5, 10, or 15 minutes -- don’t remember which), thus it really won’t start any updates expected to finish after 5:45, 5;50, or 5:55 (depending upon the time it expects for the reboot). All updates by default are expected to take 5 minutes in ConfigMgr 2012 although this can be adjusted on an update by update basis. If there are lots of updates, it’s possible they all don’t fit into the window though. J From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of James Avery Sent: Thursday, January 8, 2015 9:05 AM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Software Updates Maintenance Windows: Has to be from 5-6am no time after due to other applications happening. 1. All systems request patches from the WSUS server 2. All systems have a local GPO (workgroup computers) to tell the system to install patches at 5am. 3. Some locations are 24hrs and must have a definite time when they are scheduled for maintenance with various applications. 4. After patches are applied, all the systems reboot. With this information, there isn’t a staggers communication with the MP since all reboot within 10min of each other. James From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: Thursday, January 08, 2015 8:33 AM To: mssms@lists.myitforum.commailto:mssms@lists.myitforum.com Subject: [mssms] RE: Software Updates Maintenance Windows: The deployment start time within a MW will be as soon as the MW opens. You have to set the MW to be larger to ensure that all of the updates queued up fit within the MW because it will not attempt to install an update if the MW is too short. Thus, the size of the MW has nothing to do with start time of the deployment. Now, if a system happens to be off at 5AM but comes online within the MW, it will try to start the deployment of updates so if that’s the scenario you are trying to prevent, I don’t think there is a good way to handle that. What’s the scenario here where that requirement is valid though? Patching takes time, that’s why there are MWs. It could finish in 10 minutes or three hours later –
RE: [mssms] A tool idea related to Maintenace Widow discussion
I believe you are perfectly describing the software that 1e sells. What I've done in the past for laptops is to ignore maintenance windows, patch completely silently and do not reboot. I've never had a single complaint doing that for 8 years now. On Thu, Jan 8, 2015 at 10:54 AM, Miller, Todd todd-mil...@uiowa.edumailto:todd-mil...@uiowa.edu wrote: All the discussion of Maintenance Windows has me thinking about a significant gap in the SCCM product. Maintenance windows are pretty terrific for clients that are always on like servers, but are not so hot for clients that go to sleep. It is missing in the product to schedule a wake up at the start of the next MW if there is a deferred installation pending. It would be cool if someone with skillz could write a shim that computes whether there is a deferred installation waiting for the next MW. The shim could subscribe to sleep/shutdown event and run just prior to the machine going to sleep and schedule the computer to wake at the start of the MW if there is a deferred installation pending. It doesn’t solve the laptop problem with MWs, but it sure would make them more reliable for plugged in but sleep enabled computers. I know you can set the power settings to wake the computer up for the MW, but there are two problems with that. The first is that the computer will frequently wake up unnecessarily with no scheduled task to perform. The second problem is that the go back to sleep timer is usually set to 2 minutes which is frequently too short for SCCM to discover it has a task to run Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
RE: [mssms] A tool idea related to Maintenace Widow discussion
I do the same thing (SCCM 2007) all laptops some desktops that cannot be rebooted (1000+) apply patches during the day silently suppressing any reboots. Usually natural shutdown / restart attrition allows them to become compliant. Some users need a reminder but that is just my environment. This has worked for us for many years, we do use 1E Wakeup and Maint Windows for the other desktops across our footprint. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Marcum, John Sent: Friday, January 09, 2015 8:13 AM To: mssms@lists.myitforum.com Subject: RE: [mssms] A tool idea related to Maintenace Widow discussion I believe you are perfectly describing the software that 1e sells. What I've done in the past for laptops is to ignore maintenance windows, patch completely silently and do not reboot. I've never had a single complaint doing that for 8 years now. On Thu, Jan 8, 2015 at 10:54 AM, Miller, Todd todd-mil...@uiowa.edumailto:todd-mil...@uiowa.edu wrote: All the discussion of Maintenance Windows has me thinking about a significant gap in the SCCM product. Maintenance windows are pretty terrific for clients that are always on like servers, but are not so hot for clients that go to sleep. It is missing in the product to schedule a wake up at the start of the next MW if there is a deferred installation pending. It would be cool if someone with skillz could write a shim that computes whether there is a deferred installation waiting for the next MW. The shim could subscribe to sleep/shutdown event and run just prior to the machine going to sleep and schedule the computer to wake at the start of the MW if there is a deferred installation pending. It doesn’t solve the laptop problem with MWs, but it sure would make them more reliable for plugged in but sleep enabled computers. I know you can set the power settings to wake the computer up for the MW, but there are two problems with that. The first is that the computer will frequently wake up unnecessarily with no scheduled task to perform. The second problem is that the go back to sleep timer is usually set to 2 minutes which is frequently too short for SCCM to discover it has a task to run Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
[mssms] Re: driver package mayhem
so i did the trick of adding the blank text file to each directory in the
source folders, then reimported.
this has worked, and some kind soul wrote a batch file for the purpose, still
such an irritation, in what is a mature product.
thanks all
PUSHD %~dp0
@ECHO OFF
for /f tokens=* %%G IN ('dir /ad /b /s') DO (
echo. %%G\%~n0.txt
)
POPD?
Stuart Watret
Offshore - IT Ltd
From: listsad...@lists.myitforum.com listsad...@lists.myitforum.com on behalf
of Chris Carbone chris.carb...@fairmountsantrol.com
Sent: 09 January 2015 14:15
To: mssms@lists.myitforum.com
Subject: [mssms] RE: driver package mayhem
I have also seen this numerous times. Usually what fixes this is if you add the
ini field under drivers and delete any duplicate ini names and THEN create a
driver package the 0 byte size issue goes away. Good luck, this can be an
aggravating problem.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Stuart Watret
Sent: Friday, January 09, 2015 5:26 AM
To: mssms@lists.myitforum.com
Subject: [mssms] driver package mayhem
?TS was failing, tracked down to 7 driver packages with 0 bytes in size.
Seen this before, thought you just updated dp's and off you go, no dice.
So I have deleted all the driver packages, and the package folders (they were
blank too)
Re-creating a new driver pack for the hp 6005, wizard, says yes, package folder
is empty.
DriverCat log says, this driver has already been imported for each inf it finds.
Stuck - what now, I'd delete the drivers (under drivers) but some are shared
with other models that work.
Is there a route forward, or ditch them all and start again...
Stuart Watret
Offshore - IT Ltd
This electronic mail transmission may contain confidential information intended
only for the use of the individual(s) identified as addressee(s). If you are
not the intended recipient, you are hereby notified that any disclosure,
copying, distribution or the taking of any action in reliance on the contents
of this electronic mail transmission is strictly prohibited. If you have
received this transmission in error, please notify me by telephone immediately.
