anyweb

hmm, cleared my cache, restarted firefox, still see the old IPB one :/

seems the ico shows up correctly at http://www.windows-noob.com but as that re-directs to http://www.windows-noob.com/forums then the favico changes back to the standard one... even though i copied it to both places

welcome to the forums, to remove a patch using WSUS change the approval type on the WSUS server to 'Remove' to effect the uninstall of the update on the clients.

Opalis 6.3 introduces four new System Center Integration Packs (for SCCM, SCSM, SCVMM, and SCDPM) and updates the existing OpsMgr IP. We'll be posting a number of deep dives into the different Integration Packs to show some of the scenarios we used in creating them, but I thought that for Configuration Manager I would add a "Getting Started" article to walk through all of the different activities and how to quickly build useful workflows with them. What's In the Configuration Manager IP (with links to the TechNet docs for each): * Add Computer to Collection * Advertise Task Sequence * Create Advertisement * Create Collection * Delete Collection * Deploy Software Update * Get Advertisement Status * Get Collection Member * Get Software Update Compliance * Refresh Client * Refresh Collection Each of these activities has a specific purpose, and when combined with all of the other activities available in the base product and other Integration Packs, the potential variations are virtually limitless. It's a very flexible set of activities that addresses a specific slice of activities faced by ConfigMgr admins. Some of you may look at this list and say it addresses the majority of the things you do every day. Others may look at the list and want even more activities because you do things other than the scenarios we thought about when designing the Integration Pack. For those of you who want more, I encourage you to check out the article I wrote a couple of days ago: Making Custom Objects and Integration Packs using PowerShell Scripts. For now, let's talk about the general scenarios we were shooting for in this release. We concentrated on datacenter scenarios, but didn't forget about the client scenarios. In thinking about how customers would use this IP with Configuration Manager, these two overall themes stood out: * In the data center, Opalis provides for repeatable processes, integrated with change management, that take potential human error out of the deployment and management of critical server systems. * For client management, Opalis provides a way to increase IT efficiencies by reduce the human effort involved in handling large-scale problems like remediating client update compliance. We looked at the basic tasks that the majority of ConfigMgr admins tackle every day, and determined what kinds of Opalis activities would be useful in performing these tasks As you can see, there are a number of actions that are used across all the scenarios. We also add a couple of other utility activities: Delete Collection and Get Collection Member. The workflows I show above are very simple, but are functional as they are. All that is required is to configure the various properties of the activities. These simple workflows are actually enough to get you going with automating Configuration Manager activities like these. Of course, you'll want to add more details like error checking / handling, integration with change management, and more. Going back to my "Building Blocks" article, you can think of workflows like LEGOs, where you start with a simple configuration and then build on it to make it more sophisticated. That's what we'll explore in more detail in the next few articles. For now, this is enough to "get your feet wet" and start building workflows with Opalis to automate Configuration Manager activities. via > http://blogs.technet.com/b/opalis/archive/2010/11/21/opalis-6-3-getting-started-with-the-configuration-manager-ip.aspx

i like it, and would love it if it had a white or similar 'halo' effect, i've tried copying it to the forums root but it's not showing up, feel free to move/copy the file yourself Peter ! cheers niall

Microsoft has announced that version 6.3 of Opalis is now available for download which includes cool new features such as new Integration Packs (for ConfigMgr, DPM, SCSM & SCVMM), an updated OpsMgr Integratraion Pack for W2K8, and support of the Opalis infrastructure running on W2K8. You can find the links to the various Opalis downloads on the Opalis website at: http://www.microsoft.com/systemcenter/en/us/opalis.aspx You might also be interested in checking out the following blog post from the System Center Team blog where Adam Hall has posted some links to various interviews with those involved with the 6.3 release: http://blogs.technet.com/b/systemcenter/archive/2010/11/19/opalis-6-3-release-interviews-with-the-engineering-team.aspx

Microsoft Windows, the operating system that rose to dominance of the home and business PC market turns 25 years old today. Windows 1.0 was released on November 20, 1985, and at first didn't catch on as well as Microsoft had hoped. Two years later Microsoft would release Windows 2.0, and then Windows 3.1 which got the ball rolling. Windows 1.0 started as a graphical user interface for MS-DOS back in September 1981 and at the time named "Interface Manager." Bill Gates would later on present this development to the public on November 10 1983 where it was renamed "Windows." The name "Windows" comes from the name given to the graphic elements of individual tasks which could be moved around. Microsoft was very proud of their product, but others weren't ready to jump on the bandwagon yet, or even think there was going to be a bandwagon. Carnegie Mellon IT guy Nathaniel Borenstein didn't see Windows as anything special, and according to Gizmodo even had this to say when demoed the GUI: "We laughed, just laughed them out of the place because we had a vastly superior window manager of our own, and these guys came in with this pathetic and naïve system. We just knew they were never going to accomplish anything." Two years later Windows 1.0 shipped, but not as much more than a user interface to DOS with very limited functionality, including the inability to overlap windows. Over at Apple, in 1984 Mac OS was released, which was a functional, yet command line lacking OS. Microsoft had to play catch up and make something that wasn't strictly a GUI to MS-DOS, but that would have features of its own too. Microsoft Windows would come to be respected in the workplace with Windows 3.1, and then even more at home with the release of Windows 95. From there the next major improvement came with Windows NT which operating systems Windows 2000 and Windows XP through Windows 7 are based on, and included a new file system, NTFS. Windows has certainly come a long way in usability, concepts, looks, innovation, and even popularity from its early days. Here is to another 25 good years, you've earned it! via > http://www.neowin.net/news/windows-celebrates-25-years-of-computing

hi Bogdan, and welcome to the forums first of all, can I ask you why you want to install SQL remote ?

if you run the script in windows 7 using psexec as system, what output do you see (if any) ?

how did you uninstall office pro 2003 and how are you checking if it's installed/uninstalled ?

naturally i mean servers only and here's a query select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_R_System.OperatingSystemNameandVersion like "%Server%" and SMS_G_System_OPERATING_SYSTEM.Caption not like "%Microsoft Windows 2000%" and SMS_R_System.Active = 1 and SMS_R_System.Obsolete = 0 and SMS_R_System.ResourceDomainORWorkgroup = "xxxx" change xxxx to your Domain name, this collection will contain All servers except Windows 2000 servers. You can then target that collection with an advertisement to install the agent\ setup the advertisement with the following schedule and the code for installing the agent (can be wrapped in a vbs) check if the software is installed already If (RegistryKeyExists("HKLM\System\CurrentControlSet\Services\Healthservice\")) Then If (ManagedStateCheck(IsManaged)) Then ' Software is all ready installed WriteToEventViewer "I", PackageName, "Installation was skipped." & vbCrLf & "Server has software installed already." WScript.quit Else if it isn't, then isntall it (windows server 2008) 64 bit agent - MOMAgent64.msi ALLUSERS=2 /m MSIWQT9I /q /l*v %SYSTEMROOT%\TEMP\SMS_MOM_Agent_Install.log USE_MANUALLY_SPECIFIED_SETTINGS=0 32 bit agent - MOMAgent.msi ALLUSERS=2 /m MSIWQT9I /q /l*v %SYSTEMROOT%\TEMP\SMS_MOM_Agent_Install.log USE_MANUALLY_SPECIFIED_SETTINGS=0 you'll have to figure out what vbs or other code works best in your environment, this is just helping advice

have iphelpers been configured for this ? what router is it ? if it's linux based then options 67 will need to change direction from \ to / if i remember correctly

thats where sccm comes in, have a collection which queries if the agent is not installed if it isnt install the agent, i have a query here i'll dig it up and post it if i can find it

and theres of course this post right here on windows-noob http://www.windows-noob.com/forums/index.php?/topic/1735-using-offline-mode-in-windows-pe-using-usmt-4-via-a-task-sequence-in-sccm-2007-sp2 webcast included !

are you looking at SCCM 2012 yet ? (formally known as vNext), f.y.i i'm running a series of articles on it right here on windows-noob.com here post your experiences (if any) about it here please cheers niall

you'll need to script it so that is deleted, it's manually created, so likewise has to be manually deleted, just nevergot round to add it to my posts :/

Step 2. Add the SUP and SLP roles We will now add the Server Locator Point and Software Update Point roles to our vNext server. In the Wunderbar, click on Administration, select Site Operations, Site Roles. Right click and choose Create Roles click on browse and select our vNext server select Server Locator Point and Software Update Point and click next Accept the SLP defaults enter your proxy settings here if you have any otherwise click next select Use this server as the active software update point leave the synchronisation source settings as they are enable the schedule, the 7 day default is good enough leave Classifications as they are de-select all products (we will choose them later) Note: No updates will appear in the vNext console until you select updates from the Products list, we will do this later. make sure only English is selected click next at the summary and review the confirmation

In Part 1. of this series we Installed vNext. In Part 2., we then Configured vNext to use the New AD Site as a boundary and Configured Discovery Methods in vNext. In Part 3, we installed the Reporting Point Role along with some additional roles and configured them. In Part 4 we configured the client Agents and deployed the vNext Client. In Part 5 we deployed an Application to All Users. In Part 6 we added Windows Deployment Services, added the PSP role, added the Windows 7 Enterprise image, and updated our boot image for Deploying Windows 7. In Part 7 we created our Build and Capture Task Sequence, enabled the Network Access Account, Advertised (Deployed) the Task Sequence, and created a new hyper-v virtual machine for capturing the wim on. Step 1. Add the WSUS role to our vNext server. On our vNext server startup Server Manager. Click on Roles and click on Add Roles. click on Next at the wizard welcome page, and select Windows Server Update Services (WSUS) from the list, answer yes to the required role services you'll get a note about Web Server IIS, click next and next again Click Install when prompted and review your results when done. At this point the WSUS role will be downloaded and then installed. Depending on your internet connection this could take some time. after a while it will say Configuring and (hidden from view) will be the WSUS wizard, so click on the wizard to bring it forward you'll now see the Welcome to the WSUS 3.0 SP2 wizard click next to continue and accept the EULA accept the local download defaults (store updates locally) choose Use an Existing Database on this server and it should say successfully connected to SQL Server Instance accept the Use an existing Default website click next at the summary, click Finish followed by Cancel *you must cancel the Windows Server Update Services Configuration Wizard* finally click on Close

Step 4. Create the Deploy Windows 7 X64 Task Sequence Right Click on Task Sequences and choose Create, Task Sequence choose the first item, Install an existing image package fill in details about our image and select the X64 boot image by clicking on Browse on the Install the Windows Operating System image screen appears, click browse select our image make sure to select the option Always use the same Administrator Password (useful for troubleshooting failed deployments, can be changed later via a script or gpo) for Configure The Network, select your domain and enter a user with permissions to join the Domain (domjoin) click on browse and select our Configuration Manager Client package we created earlier for State Migration select our USMT 4 package which we created above by clicking on browse for updates in the image, choose All Software Updates for applications don't select any for now ! click next at the summary, review the progress and close at the confirmation

Step 2. Distribute the image to Distribution Points Highligh our newly created image and right click, choose Distribute Content click on the Add drop down menu and choose Distribution Points as this is not a boot image, select only the standard DP's Click Ok and OK again. Step 3. Create the USMT 4 Package In Application Management, right click on Packages and choose Create Fill in details about the USMT package, and for source, point to the following path C:\Program Files\Windows AIK\Tools\USMT Choose Create No Program for this package as none is required click next at the summary screen and click close at the confirmation Note: Don't forget to Distribute your USMT package to your Distribution Points, to do so follow the way we did above for distributing the Operating System Image (click on Distribute Content and follow the wizard).

using diskpart, what partitions are on the computer you are trying to capture ? this is a very good reason NOT to be doing it this way, much better to automate it 100% using a build and capture tasksequence which creates your master image (the one you are trying to capture now), you can then tweak that to your hearts content later on down the line, try tweaking the current image you have (which someone else made... ) in a repeatable way ... not so easy.

sounds like you havnt loaded network drivers in your boot.wim, enable F8 support bring up the command prompt in winpe and type ipconfig to find out

first of all, why have you not extended the Schema ? is anything stopping you from doing so ?

In Part 1. of this series we Installed vNext. In Part 2., we then Configured vNext to use the New AD Site as a boundary and Configured Discovery Methods in vNext. In Part 3, we installed the Reporting Point Role along with some additional roles and configured them. In Part 4 we configured the client Agents and deployed the vNext Client. In Part 5 we deployed an Application to All Users. In Part 6 we added Windows Deployment Services, added the PSP role, added the Windows 7 Enterprise image, and updated our boot image for Deploying Windows 7. In Part 7 we created our Build and Capture Task Sequence, enabled the Network Access Account, Advertised (Deployed) the Task Sequence, and created a new hyper-v virtual machine for capturing the wim on. In Part 8 we installed WSUS and then the SUP and SLP roles. In Part 9 we configured SUP and deployed some updates. Now we want to deploy our captured Windows 7 image using a separate Deploy Windows 7 Task Sequence. Step 1. Import the Captured Image In Software Librady, Expand Operating Systems, and right click on Operating System Images, choose Add Operating System image fill in some details about your master image and click Close at the confirmation screen Browse to the previously captured WIM file Fill in some details about the image and proceed with the wizard through to the confirmation screen, click close when done.

well 5000 clients can be managed no problem by one SUP, what do you mean 'faster updates' ?