anyweb

can you enable verbose logging, and paste any relevant parts from scanstate.log, scanstateprogress.log please ? does it mention capturing your network settings, if so perhaps we only have a loadstate problem

well the advantage of hyperV is that it's a Microsoft product and definetly good to familiarise yourself with, everyone and their neighbor is a vmware expert these days i've used both vmware (esxi/workstation) and hyperV and i actually prefer using hyperV, I use it for all my labs cheers niall

welcome Peter ! you know we are happy to help have you tried server 2008 r2 yet ? it's great, and if you have a laptop/desktop that is virtual capable (cpu...) then you can install hyperV and run all your testing on that, that's the way i do it (virtual machines in hyperV), cheers niall

Web services are all around us, and with the proliferation of Cloud computing (and the Microsoft strategy for Public and Private Cloud), use of web services will become more-and-more common over time. In this 3-part series, I am going to drill down into Opalis web services capabilities and share some tips, including: * Making web service calls with Opalis * Dissecting the XML Response Payload * How to construct queries to retrieve targeted values * Pushing the limits – What to do when ‘Invoke Web Service’ isn’t enough In the Series * Part 1: Making Calls and Parsing Output * Part 2: When Invoke Web Services Isn’t Enough * Part 3: XPath Query Primer In this Installment Okay, time to get started. Let’s quickly look at the topics for this article and then we’ll get down to business. * Scenario and Sample Workflow * Object Configuration * Viewing the XML Response Payload * Extracting Data of the XML Response Payload * Presenting Results Scenario and Sample Workflow We’ll begin with an explanation of the Opalis policy (workflow). Here is a workflow that queries a web service (a stock quote service) to retrieve details about the stock performance of a particular company. Objectives for this Workflow: * Call the web service * Pass in a stock ticker symbol to retrieve info about a target company * Parse the XML output (the response payload) to extract specific information: o Full Company Name o Current Price o Price-to-Earnings (PE) Ratio * Present this data in a nicely formatted pop-up message NOTE: The Custom Start object at the beginning of the workflow is there so we can run this workflow on demand from the UI or externally through command line or the Opalis web service. read the rest here > http://www.systemcentercentral.com/blogs/administrator/archive/tags/powershell/BlogDetails/tabid/143/IndexID/83740/Default.aspx?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+systemcenterforum+%28SystemCenterForum.org+Rollup%29&utm_content=Twitter

Microsoft demonstrated at a press conference on January 5 the “next version of Windows” running on ARM processors, as many Microsoft watchers had been expecting. At the press conference — held a few hours before CEO Steve Ballmer will keynote the Consumer Electronics Show (CES) — Microsoft Windows President Steven Sinofsky showed off an early build of Windows 8 runnong on new systems-on-a-chip (SoC) platforms from NVIDIA, Qualcomm and Texas Instruments on ARM. To prove Microsoft isn’t abandonning the x86 architecture with Windows 8, company officials also showed off Windows 8 running on x86 SOC. Rumors that Microsoft would show off Windows 8 running on ARM have been circulating for the past couple of weeks. Earlier this week, TechFlash reported that Microsoft had cut deals with the aforementioned ARM chip makers, which will enable Windows 8 to run on ARM-based systems once the next release of Microsoft’s operating system is available. Sinofsky told press conference attendees they were forbidden from videotaping demos of the next version of Windows. Unsurprisingly, he also said Microsoft would not discuss its release schedule plans or show off the new Windows 8 user interface. Microsoft has been working to port Windows to ARM for several years. I had heard about LongARM, a project to port Vista (codenamed Longhorn) to ARM a while back. Microsoft last year signed an architecture licensing agreement with ARM, but wouldn’t say anything about its plans at that time. Microsoft is believed to be finally backing ARM as that low-power processor is especially well suited to tablets and slates, which are one of the primary form factors Microsoft plans to target with Windows 8. Windows 8, according to my tipsters, is just around the Milestone 2 mark, which is the second major internal build for the operating system. A public test build of Windows 8 isn’t expected by most until later this year. Microsoft officials have continued to say when the company is planning to ship WIndows 8. GIven that Windows 7 was released to manufacturing in July 2009, one would think a 2012 launch date is a possibility. (I have heard from some that Microsoft, once it does talk dates, may say 2013 to eliminate any possibility of being “late.”) Update: More from the Microsoft CES press conference and press releases: * Sinofsky said that “normal” Windows software will continue to run on Intel’s SOC with the next version of Windows without requiring any rewrites. * Sinofsky also said Microsoft will insure that Office, going forward, will run on ARM SOC systems. via > http://www.zdnet.com/blog/microsoft/ces-microsoft-shows-off-windows-8-on-arm

Watch Steve Ballmer's CES Keynote On-Demand Jan. 5, 2011 Watch the full on-demand video of Microsoft CEO Steve Ballmer's opening keynote address at 2011 CES on Wednesday evening in Las Vegas. On-Demand: Keynote Address Transcript: Steve Ballmer Keynote via > http://www.microsoft.com/presspass/events/ces/

we'll still be here when you come back to SCCM, by the way, did you ever manage to see what the SMSTS.log file said ? cheers niall.

check the sup component classifications, is Office 2010 enabled ?

you'll need the original sccm installation media, its on technet/msdn if you cannot find it. and as i said before we'll help you with this but you must be patient with it, especially in the beginning with OSD cheers niall

get your sccm 2007 sp2 media, as it's similar to installing a site, except choose to Install the console. see pic

can you please try these search folder criteria, does it help ? Product=Office 2010

you dont need to insert a usb key in the server, just install the sccm console on your desktop (windows xp/7) and create the key there..

well try the custom capture windows 7 task sequence then...

ok then, let's try and fix the problem, what OS are you trying to capture ? you can try using this custom task sequence to capture windows 7, or is it XP ? there are many way's to capture an image to WIM file but it is not the same thing as a ghost file (gho), ghost is bit by bit, WIM is files... let us know.. cheers niall

what office 2010 updates are you expecting to see ?

as regards your errors, 0x00000032 means not supported, 0x00000001 means incorrect function. Chris is just trying to help and you are most likely so frustrated with trying to get the job done that you failed to understand that, the SMSTS.log file can be found/accessed by reading this post after working with SCCM for some months/years you'll soon realise that it is a far better tool for the job than Ghost could ever be, as you can automate everything from start to finish in a repeatable way, I'd recommend you go the build and capture route, start from scratch, learn what you hve to learn and understand that Ghost's way of doing things may be fine for small deployments but is not diverse enough to allow you to take control of an enterprise. Sccm (Configmanager) will handle small deployments and very big ones too, and learning how to do build and capture will teach you loads about the process's involved and how to streamline everything. we will help you if you are willing, cheers niall

good work, please post the lines you added so others will learn cheers niall

I've upgraded the forums server software and it means new features as well as being up to date ! you'll notice that you can now twitter/facebook/digg/buzz up new posts by clicking on the relevant pic beneath your post amongst other new features, please tell me if there are any problems found cheers niall

Test the Office 2010 Deployment Now that we have the groundwork done, you'll want to test the package on some Windows 7 clients. To do so you could use direct membership to add those computers to the Office 2010 collection, or better yet, setup a query on the collection and use Active Directory Group Membership to do it for you. But for the purpose of this guide, let's add a virtual machine (Windows 7) to our Office 2010 collection using direct membership. right click on your Office 2010 collection and choose properties click on the Membership Rules tab, then click on the new direct membership button in the create direct membership wizard, use the drop down menus to select Resource Class: System Resource Attribute Name: Netbios Name Value: Win7client01 input the values to match your computername you wish to test... in my case I used a virtual machine called win7client01 click next at collection limiting and on the Select resources screen, place a checkmark on the clients you want to add to the collection click finish to exit the wizard. On your Windows 7 client, monitor it until you see the New Program Notification prompt (or you can go into Configuration Manager Client, Actions tab and kick off the Machine Policy retrieval to speed things up). The program becomes available in RAP. Select it and click Run due to our Advertisements distribution settings for the package, we are informed that the program must be downloaded before being run. This is the desired effect as we do not want it to start downloading and have users interupt the process midway by turning off. They can do so with this setting and it will resume the next time they start the computer. click on Download and the program download begins when the Program is fully downloaded you'll be informed that it is ready to run. Click on Run. At this point Office 2010 is being installed in the background silently unless of course you are having a problem, in which case you should check the following folder on the client. C:\Windows\Temp Look for the setupexe log and check it to determine if there are any failure messages. All things should go well however and Office 2010 will be installed ! Further reading:- Technet: Troubleshooting a Configuration Manager 2007 Installation of Office 2010

Step 4. Advertise the Office 2010 Package Ok you've nearly got everything in place, now you want to advertise the Package to a collection, if you havn't already done so create a collection called Office 2010. Expand software distribution and select Advertisements, right click on advertisements and select new advertisement. fill in the details Name=Microsoft Office 2010 Professional Plus Package=Microsoft Office 2010 Professional Plus X86 English Program=Microsoft Office 2010 Professional Plus Collection=Office 2010 We want the schedule to be optional, so leave it as it is set the Distribution Point settings as follows and click through to the confirmation screen click close to finish.

Step 3. Distribute to Distribution Points We now need to copy our package to the distribution points serving our clients. Select our package, right click on distribution Points and select New Distribution Point. click next at the welcome, then select your Distribution Points from the list (don't select any SMSPXE dps) click close at the confirmation screen.

Step 2. Create the Office 2010 Program. Select our newly created package from above, expand it, right click on Programs and choose New Program fill in your program details enter your desired requirements, here you can limit the program availability to All Windows 7 X64 and All Windows 7 X86, set the Environment to run Whether or not a user is logged on and make sure that 'allow users to' is NOT selected. for the Advanced properties, set allow this program to be installed from the Install software task sequence without being advertised and then click next through to the confirmation screen. click Close.

In part one of this guide, we prepared Office 2010 X86 by downloading the files required (including the OCT), and created our own MSP file. Now we will add that customised package to ConfigMgr. Step 1. Create the Office 2010 Package Note: Before starting this step, copy the c:\Office2010x86 folder we created in part one of this guide, to your application sources share on your SCCM server, eg: \\WIN-CILZXI45G1Q\apps\office2010x86 Open your ConfigMgr console, and expand Computer Management, Software Distribution. Right click on Packages and choose New Package. Fill in your package details on the wizard screen point it to the data source on your network share and click next through the wizard until you see the confirmation screen.

here's how eg: /config:\\bla.windows-noob.lab.local\SMSPKGE$\CEN00070\amd64\Config.xml