Jump to content


dsmonroe63

Established Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by dsmonroe63

  1. On 5/8/2016 at 0:29 PM, GarthMJ said:

    If you are looking to get better writing reports, first I will tell you to stop using Report Builder and use SQL Server Data tools (SSDT) or Business Intelligence Development Studio (BIDS) instead.

     

    If you will be at MMS next week there are several presentation on writing reports.

     

    Lastly, if you are looking for a book on the subject then I would look at this one. :-)

    http://www.amazon.com/gp/offer-listing/0672337789

    What would you know about repor---

    *sees it's Garth Jones replying, fangirling begins*

    THANKS!

  2. I know this post is ages old but it helped me! We started getting sync errors as described above. I finally noticed the 6703 errors (duh). For some reason, we had WSUS installed on the Primary and not configured since the SUP was on another server entirely. I deleted WSUS from the Primary and all was well again. I also felt a little silly for not noticing it earlier... :unsure:

    Thanks!

  3. On 11/14/2013 at 6:44 PM, learningmode said:

    Okay, resolution to this was to basically create a new Configuration Manager Package which I did do, but what Microsoft did was basically Re-Create the Client Package as if we built in the CAS. Since my Client package was created in the Stand Alone initially and was Expanded to the CAS it might have caused some issues??? I don't really totally agree with that, but oh well.

    I did this for a problem I had and it worked great. Thanks for your help!

  4. Hey all, a week or so ago, I started removing old content from distribution points as part of a site clean up. I made a major mistake by not querying which packages are needed by task sequences. At some point, the number for the Configuration Manager Client Package and the Upgrade Package got changed from the default of XXX00003 and XXX00004 to something else and I didn't notice the name. I removed the packages from two DPs using PowerShell. Seeing they were missing, I attempted to redistribute. No luck. Not only do they not redistribute but every half hour or so they are 'successfully removed' from the two DPs:

    Distribution Manager successfully removed package "XXX0001F" from distribution point "["Display=\\DISTRIBUTIONPOINT\"]MSWNET:["SMS_SITE=WHQ"]\\DP.FQDN.LOCAL\".

    I've attempted to add 'client.acu' into the Hman Inbox, I've added a .txt file to the package source to make the package different so it would redistribute, and I've tried to force the distribution with PowerShell. No luck. 

    Any ideas? I'm tempted to try this solution but wanted to get all of your thoughts first. Thanks!

    distmgr.log

  5. Replace 'ES-06' with @PC

     

    This will create a prompt for the report. If you want to make it fancy you can then add a drop down or browse list for the PC name.

     

     

     

    The easiest way to convert your CM07 to CM12 report is to make sure that you have already converted them from ASP to SSRS then you can upload the same converted reports to CM12. Other than that, I your recommend rebuilding them and filtering out all the old junky reports.

     

    I'm wanting to create this report and let server owners search for their servers so they know what time their servers get patched. (Should they know this already? That's for another thread...) What do I need to put in my parameter to create that drop down menu so they can search? The query works great, I'm just not so great with Report Builder yet. Thanks!

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.