Monthly Archives: February 2013

If you have signed up for Office 365 and provisioned user accounts for the users in your organization, you can enable users to install Office 365 ProPlus (and Project Pro, Visio Pro, SharePoint Designer, or Lync products) directly from the Office 365 portal. This is the default option. In managed enterprise environments, end-users may not have permission to install software from the Office 365 portal. Administrators can use the Office Deployment Tool to manage Click-to-Run installations.
To customize a Click-to-Run for Office 365 installation, administrators run the Office Deployment Tool and provide a custom Configuration.xml configuration file. The Office Deployment Tool performs the tasks that are specified by using the optional properties in the configuration file.
For the Office 2013 release, administrators can run the Office Deployment Tool to perform the following tasks:

In some scenarios in Configuration Manager 2012 you want your packages, OS images, boot image and driver packages, well everything you use in a task sequence to be available on the package share so that we can use the option to access the content directly during OS deployment.
This of course takes up more disk space but makes the OS deployment a little bit faster.

Here is the setting in question:

I got a question today if you could script that setting, so after a little bit of WMI browsing I found the value that needs to changed, as I couldn’t find it in the SDK for Configuration Manager 2012, maybe I wasn’t looking hard enough. Erectiestoornis diabetes

This book is a great book if you want to get started with Configuration Manager 2012! It is well written by experienced professionals (Brian Mason and Greg Ramsey both MVP’s) with tons of experience, with a focus on getting you started and explaining why you do the things you do.

Configuration Manager 2012 is a very complex product so it can be a real challenge the first time you start using it. I really like that each feature covered in the book is divided in “Getting ready”, “How to do it”, “How it Works”, it makes it much easier to get an understanding how it actually works.Administration-Cookbook_cov

Impotentie na prostaatoperatie

There are some interesting reading in the supported configurations for WSUS in Server 2012 which is useful to know when you design your Configuration Manager 2012 environment with a Software Update role. I normally use the same SQL for WSUS as I use for Configuration Manager 2012 in many designs at customers. However there are some interesting reading on Technet about supported databases.

Right now Microsoft SQL Server 2012 is not supported so keep that in mind when upgrading your SQL or designing your Configuration Manager 2012 SP1 environment. Continue reading

Different scripts before to install all the prereqs needed for Configuration Manager in different versions. There are great hydration kits out there which can be used to install a Configuration Manager 2012 environment, but if you only want to install all pre-reqs needed by System Center 2012 Configuration Manager SP1 on Windows Server 2012 then you can use this Powershell script.
Note that you need to supply a path to the binaries for .NET Framework 3.5 which is located in the Server 2012 installation media under \sources\sxs\ Continue reading

In some scenarios you need to install the SCCM client using another Software Distribution tool than Configuration Manager, yes I know it sounds strange ;-)

If you have tried this you know that the Ccmsetup.exe installs a service and the exits in the user context so that control is returned to the vbscript, cmd file or whatever method you use to run Ccmsetup.

There are two ways of solving this:

1. Run Ccmsetup.exe with the /noservice switch then ccmsetup runs the setup in the user with which you triggered the installation and not using  a service in System context. Watermeloen natuurlijke viagra

The Server Locator Point is no more a separate site system role in SCCM 2012. It’s functionality is merged into the Management Point.
To install CM12 client on workgroup machines:
1. Make sure your Management Point is published on DNS or WINS
2. Make sure Management Point FQDN can be resolved from the client machine
3. For the client installation on Workgroup machines use the CCMSetup.exe with local Administrator previledge Impotentie pillen

Is the Microsoft Surface the next killer tablet? All these “killer this” and “killer that” comparisons get out of control. Every new challenger is hyped as the killer of what came before. But sometimes, it’s true. The iPad really turned out to be a PC killer. People bought iPads instead of buying new PCs, and that market took a pretty big hit. Apple pulled this off by building something that changed the rules for a PC, and we saw it differently. Erectiestoornis diabetes