anyweb

Microsoft plans to offer one more public test version of Internet Explorer 8 before releasing the final version of the updated browser, the company said late Wednesday. The next test, essentially a "release candidate" version will come in the first quarter of 2009. That means the final release won't hit Microsoft's initial goal of finishing the browser this year. "Our next public release of IE (typically called a "release candidate") indicates the end of the beta period," general manager Dean Hachamovitch said in a blog posting, "We want the technical community of people and organizations interested in Web browsers to take this update as a strong signal that IE8 is effectively complete and done." via osnews.com

got this error last night while trying to install software (ignore the fact that I mention a hotfix, it actually doesnt matter), it turns out it failed because i hadn't defined my regional settings in the test task sequence, meaning that the SCCM server and Client were about 8 hours apart time wise, once I set the timezone in the task sequence to the same as the server I was deploying, the error disappeared and the TS completed normally.

Overview This software development kit (SDK) contains documentation and samples for developing Configuration Manager 2007 applications that integrate with the Configuration Manager console, the SMS Provider (server-side applications), and the client-side applications. The SDK enables developers to build plug-ins for the Configuration Manager console, to build automation scripts for batch processing to the SMS Provider, and to manipulate client settings. Top of page System Requirements Supported Operating Systems: Windows Server 2003 System Center Configuration Manager 2007 Microsoft Visual Studio 2005 Microsoft Management Console 3.0 Microsoft .NET Framework version 2.0 download it here

is SCCM installed on the server that you are attempting to locate this information on ? the SMS_* groups are created when SCCM is installed... you are looking in Active Directory users and Computers in the USERS section arnt you ???? give me more details please cheers anyweb

those of you used to Microsoft Virtual PC will find it odd that you can no longer drag and drop files from your desktop to the virtual machine in Hyper V, but all is not lost, you can copy/paste files to/from the Virtual machine by using standard network sharing, in the screenshot below I first connected to my virtual machine using Windows Explorer and browsed to the C$ share on the virtual machine, i then dragged a file from my desktop to that share, and you can see the file is present locally on the virtual machine which is also shown on the desktop (to the right) f.y.i

This Configuration Pack helps track configuration compliance for your Configuration Manager 2007 site server roles, such as management points, distribution points, and software update points. Overview Software installation errors and misconfigurations compromise security and stability, resulting in escalated support costs. The System Center Configuration Manager 2007 Configuration Pack can help prevent errors, increasing your organizational uptime and helping you build a more secure and reliable Configuration Manager 2007 infrastructure. This Configuration Pack contains Configuration Items intended to manage your Configuration Manager 2007 site system roles using the desired configuration management component in Configuration Manager 2007. This configuration pack monitors the following site system roles: management points, distribution points, and software update points. The Configuration Pack can also monitor Windows Server Update Services (WSUS) components on software update points or upstream WSUS servers. To manage your site system roles with this Configuration Pack, import and assign the Microsoft System Center Configuration Manager 2007 Server Roles configuration baseline to a collection which contains your Configuration Manager 2007 site systems. While there is one configuration baseline for all site systems, it evaluates compliance only for roles configured on the site system. For example, if a computer has only the distribution point role, it will not be evaluated for management point configurations. To understand in detail what each configuration item will be evaluating, review the properties of that configuration Iitem in the context of the Configuration Manager 2007 Server Role being addressed. System Center Configuration Manager 2007 site roles covered: • Management points • Distribution points • Software update points download it here

This Configuration Pack helps track common software mis-configurations which might make client computers more vulnerable to attack. Software installation errors and misconfigurations compromise security and stability, resulting in escalated support costs. System Center Configuration Manager 2007 Vulnerability Assessment Configuration Pack can help prevent errors, increasing your organizational uptime and helping you build a more secure infrastructure. This configuration pack provides vulnerability assessment reporting for common software misconfigurations using the desired configuration management component in Configuration Manager 2007. The Configuration Manager 2007 Vulnerability Assessment Configuration Pack monitors the configuration of Microsoft Windows operating systems, Internet Explorer, Microsoft Office, SQL Server, and Internet Information Services (IIS). To use this Configuration Pack, import and assign the three configuration baselines (Vulnerability Assessment: IIS Baseline, Vulnerability Assessment: SQL Server Baseline, Vulnerability Assessment: Windows Baseline) to a collection containing the computers you want to monitor. To understand in detail what each configuration item will be evaluating, review the properties of the configuration item. Scenarios: • Scan for potential security issues that may exist because of misconfigurations. • Example checks: o Are unnecessary services installed and running? o Do shared folders have appropriate permissions? o Is Windows Firewall enabled? o Are strong passwords enforced? o Are unsecured guest accounts enabled? download it here

WELCOME Znapper ! I'm really looking forward to seeing your exchange stuff ! cheers anyweb

Note: if you are going to use SCCM to manage patch management, then do NOT run the WSUS configuration wizard below Starting WSUS for the first time Click on Start/All Programs/Administrative tools/Microsoft Windows Server Update Services 3.0 SP1 this will start a wizard (pictured below) click next choose to opt in or opt out (default is opt in) Next you can choose your Upstream Server, I stayed with the default option enter your proxy settings (if any) click next and then start connecting once the Wizard has synchronized information with the Microsoft Update web servers you can click next to continue next you get to choose which languages to support and which Microsoft Products to support by default all office versions and all windows versions are selected, remove those which you don't need as all of these updates etc will take up storage space next you can choose what type of updates to download pick a schedule to synchronise finished ! review next steps and then click on Finish to end the wizard. At this point you can now use the WSUS UI Troubleshooting: verify the following LOGS to see how WSUS installation went. MWusSetup.log WSUSSetup.log WSUSSetupmsi_100211_2212.log the last LOG will have it's name based upon the installation date/time as you can see. These logs will be found in the users AppData\Local\Temp folder eg: if the user that installed WSUS was SMSadmin then these logs will be found here: C:\Users\smsadmin\AppData\Local\Temp\ next steps >> how can I configure WSUS to deploy updates

did you verify you have advanced view turned on in AD users and computers...

if you want to install msu update files then you can use WUSA to do the job eg: wusa "Windows6.0-KB934307-x86.msu" /quiet /norestart the /quiet switch means no user interaction and the /norestart means just that you can add this to a task sequence

can you take a screenshot of your task sequence and/or export it to xml and attach it here ?

If you have just installed Hyper V in Windows 2008 Server and start a new VM and click on it's settings, you may notice that the network adapater does not have any option except 'Not Connected' in the drop down menu. The solution is simple enough go into Hyper V Managerand right click on your Server (or in the Actions Pane on the right), choose Virtual network Manager, click Add, and choose an External, Internal or Private network, give it a name (like Local network only...) once done click apply, Now go back to your VM and click on settings, Network Adapter, you should now be able to choose the drop down menu and select the new virtual network you just created cheers anyweb

as regards the admin password did you check this ? (below the red circle...)

which admin account are you talking about ? the built in Administrator account or some other one that you created ?

how are you installing the image ? is the image already created ?

so let me get this straight, you are mounting boot.wim and writing the new driver to it, then unmounting the file with the changes (using imagex) or are you doing this another way ?

great that it's working now, so it was just the network access account not being specified I've updated that section in the Setting up SCCM guide part 3 cheers anyweb

hi again let's take that question as a separate topic please to keep this one focused cheers anyweb

This guide assumes that you intend on using WSUS to deploy updates and that you have already installed it as outlined here. NOTE: this post is NOT FINISHED YET so it is INCOMPLETE Note: If you intend on using SCCM 2007 to deploy updates using the WSUS integration then do NOT do any of the steps here. The instructions here also assume that your network runs Active Directory and that you use Group Policy to manage your network. For more information about Group Policy, see Microsofts Group Policy home page. You can configure one or more computers by including them in a Group Policy object (GPO). By configuring Automatic Updates using Group Policy, these settings will take precedence over any settings that are defined locally on the computers within your Domain. Note: You should Link this WSUS GPO to an Active Directory container appropriate for your environment. In a simple environment, you link a single WSUS GPO to the domain. In a more complex environment, you might link multiple WSUS GPOs to different organizational units (OUs). Start the Group Policy Management MMC and highlight your domain as in the screenshot below. Right-click the domain and choose Create a GPO in this domain, and link it here When the New Group Policy Object window appears, give it a name like WSUS GPO and click OK right click on our new GPO and choose Edit expand Policies then click and highlight Administrative Templates. Before you can configure WSUS group policy settings you should load the latest version of the administrative template, wuau.adm. Right click on Administrative Templates and choose Add/Remove Templates, click on the Add button and scroll down to the bottom until you can see the wuau.adm file. Select the file and click Open and close. Now that you have loaded the wuau.adm template, you are ready to expand Windows Components. Scroll down to Windows Update and enable the following options (circled in Red) Automatic Updates are now enabled, but before the computers can receive updates from the WSUS server we need to configure the following group policy setting: Specify intranet Microsoft Update service location and fill in the https address of the WSUS server, so click on it and view it's properties. We have already enabled the group policy setting as in the screenshot above, however we need to enter the https address of our WSUS server, so do that in the two empty fields provided and click ok. Startup WSUS

can you please read the package status LOGS for the package in question, it should give us a clue, in addition, please distribute the package again, and update the distribution point before trying again cheers anyweb

what does your package status say for that package ? any errors reported ? you can check the package status in the SCCM console under 'status...'

here is where you are having problems (the screenshot is of Trace32 part of the SCCM2007 toolkit, it highlights errors in logs in RED) the first error is so what is that package ? please verify that it is distributed to a distribution point (check the package status) the error above means it cannot find this packagepossible reasons are boot.wim has no network support for your nic or you havnt distributed the package properly (or need to do it again) this is where the Task Sequence aborts, it cannot continue because it cannot get some package(s) cheers anyweb

ok if its still failing just after starting windows PE with a reboot, then press F8 like i said, which will bring up a cmd prompt within windows PE copy any log files that are in there, zip them up and post them here, (The logs for SCCM (in this case) are stored in X:\Windows\Temp\SMSTSLog\ and C:\SMSTSLog and C:\_SMSTaskSequence) i need to see those logs to understand what is failing cheers anyweb

dont worry about that, i've also seen that when deploying clients, it doesnt matter as long as youve created boot.wims for both architecture (32 bit and 64bit) and that you have defined what operating system is being installed cheers anyweb