[WP7] Nodo update for Windows Phone

By StijnC at April 01, 2011 09:12
Filed Under: Windows Phone 7

The March update of Windows Phone 7 being released to the public sure got me exited, finally we’ll have copy/paste at our disposal.

 

Currently my carrier is still in a testing stage of the NoDo update, but using a little trick does the job and grants access to the update.

As of this writing, my phone is updating:

image

 

Steps are available on Paul’s website via Neowin

 

Enjoy!

[Powershell]

By StijnC at June 24, 2010 09:33
Filed Under: Powershell, Microsoft, Update

The Powershell team released Windows PowerShell 2.0 and WinRM 2.0 for pre-Windows 7 operating systems on Windows Update. This non-security, optional update is designed for Windows Server 2008 SP2, Windows Vista SP2, Windows Server 2003 SP2, and Windows XP SP3.

Windows PowerShell 2.0 and WinRM 2.0 are also available as part of  the Windows Management Framework (WMF) Core Package on the  Microsoft Download Center and Windows Server Update Services (WSUS).

The WMF Core Package available on the Microsoft Download Center and the Windows Update release contain the same binaries of the products, so you can now download them from either source. Because Windows PowerShell 2.0 is in-place upgrade to Windows PowerShell 1.0, we will no longer be offering Windows PowerShell 1.0 on Windows Update.

Windows PowerShell 2.0 appears as an option in a Windows Update scan only if the computer meets the following conditions.

  • The computer has at least Microsoft .NET Framework 2.0 SP1
  • The computer does not have a non-RTM (CTP, Beta, RCs etc.) release of Windows PowerShell. (Windows PowerShell 1.0 RTM can be installed.)

as found on the Powershell Team blog.

[Powershell] The scripting games 2010 are a wrap!

By StijnC at May 18, 2010 09:40
Filed Under: Powershell, Scripting Games 2010

2010_scriptgames_postgames The scripting games took place from 26th of April to May 7.
Although I sometimes struggled to get the scripts submitted on time,I really need to start working on my time management skills :), it was a lot of fun.
This is actually the first time I participated in this event and I was a awesome experience!
The community participating was all around twitter and the forums, any questions asked where rapidly answered,… etc.

I also liked the idea that multiple judges grated the scripts submitted. As there are several approaches you can tackle a problem, your vision might not always be the most efficient.
This actually brings me to the only drawback of the 2010 Scripting Games. If a second opinion would result in a downgrade of your script, it’s useful to have the ‘why’ communicated.

The greatest advantage of participating really comes down to one thing: I learned a lot.
The events were challenging and forced me to start exploring new items (like remoting, winforms/WPF,…), searching for useful information and so on.
Powershell is not about reading a book but getting your hands dirty and the 2010 Scripting Games provided that opportunity whether you’re a novice or advanced scripter.

Anyway, all things need improvement but already now this experience was top of the bill!
See you all again next year!

Thanks to:
The judges,
The sponsors,
The Scripting Guys
And all the other I forgot

 

 

[App-V] Application Virtualization Sequencing SuperFlow

By StijnC at April 28, 2010 08:05
Filed Under: Documentation, App-V

The SuperFlow interactive content model provides a structured and interactive interface for viewing documentation.

Each SuperFlow includes comprehensive information about a specific dataflow, workflow, or process. Depending on the focus of the SuperFlow, you will find overview information, steps that include detailed information, procedures, sample log entries, best practices, real-world scenarios, troubleshooting information, security information, animations, or other information.

Each SuperFlow also includes links to relevant resources, such as Web sites or local files that are copied to your computer when you install the SuperFlow.

This SuperFlow provides detailed information about the Application Virtualization Sequencing process.

Download the superflow

[Software] McAfee Antivirus deleting svchost.exe

By StijnC at April 23, 2010 11:25
Filed Under: Antivirus

found on Ask the core team
Summary

McAfee has identified an issue with the a Virus Definition (DAT) file which causes a false positive detection of the w32/wecorl.a virus in svchost.exe.   When this false positive occurs, svchost.exe may be quarantined or removed depending on software configuration.  This can cause the computer to shut down with a DCOM or RPC error, remain running without network connectivity, or in some circumstances trigger a Bugcheck.  Windows XP SP3 is the only affected operating system which has been identified.

Resolution

To manually repair a computer which is not-functioning due to this issue, follow the steps below:

   1.  Restart the computer in Safe Mode by pressing F8 before the Windows splash screen.
   2.  Log into the machine, then press CTRL+ALT+DEL and start Task Manager
   3.  Select New Task (Run…) from the File menu
   4.  Type cmd.exe and press ENTER
   5.  Type ren “%programfiles%\Common Files\McAfee\Engine\avvscan.dat” avvscan.old
NOTE: This will remove McAfee virus definitions.  Make sure to update
       to the latest (5959 DAT or newer) definitions after completing these steps
       to restore virus definitions.
   6.  Type copy %systemroot%\system32\dllcache\svchost.exe %systemroot%\system32\
       and press ENTER
   7.  Restart the computer

For a tasksequence approach, browse the Configuration Manager team blog.

McAfee articles:
https://kc.mcafee.com/corporate/index?page=content&id=KB68780
https://kc.mcafee.com/corporate/index?page=content&id=KB51109

[Office] Office 2010 goes RTM

By StijnC at April 23, 2010 11:25
Filed Under: Microsoft, Office

MS-Office-2010-logo-mockup

Office 2010 now availble on Technet and MSDN





 

 

 

 

 

 

[SCUG] Best of MMS 2010

By StijnC at April 23, 2010 11:21
Filed Under: MMS, Event

Best of Microsoft Management Summit 2010

Best of MMS 2010 will provide the opportunity to learn more about IT Management solutions from Microsoft and how you can adopt them in your datacenter. MMS is an annual event in Las Vegas where we deliver deep technical content on our latest management solution offering.

In a year packed with new management product releases, MMS 2010 will provide the latest technical updates on Desktop, Datacenter, Device and Cloud management features and solutions from Microsoft. This year 5 of our Belgian Experts from the System Center User Group will attend this event and bring back all the valuable information and present them to the Belgian IT Professionals.

register now!

Date:
May 11,2010

Location:
Microsoft Office
Da Vincilaan 3
1935 Zaventem

[TechNet Webcast] System Center and the Green Client

By StijnC at April 23, 2010 11:21
Filed Under: Configuration Manager, Event

With the release of the Windows 7 operating system, new capabilities, working scenarios, and efficiencies are emerging. In the area of green IT, Windows 7 contains new features that, when combined with Microsoft System Center, drive the reduction of operational costs through centrally controlled power management. 

In this webcast, we describe the enterprise-class power management capabilities that were introduced in the newly released Microsoft System Center Configuration Manager 2007 Service Pack 2 (SP2) and Configuration Manager 2007 R3. From integration with Intel vPro technology, to power management planning, to centrally controlled policy application, to industry-standard reporting formats, join us to learn why Configuration Manager should be your technology of choice to help reduce energy costs.

System Center and the Green Client (Level 300)

Duration:
60 Minutes

Date:
Monday, May 24, 2010

[Beta] Configuration Manager R3 beta Available

By StijnC at April 23, 2010 11:20
Filed Under: Configuration Manager, Beta

As announced by Brad Anderson at MMS 2010 the R3 Beta is now available for download from the Microsoft Connect Site.

To download R3:

  1. Goto https://connect.microsoft.com/site16
  2. Sign in to the site
  3. Download the bits

the key improvements are:

• Monitoring and Planning: The Power Management feature collects information about computer usage and power settings for computers in the origination.  Reports are provided to allow the administrator to analyze this data and determine optimal power management settings for computers.

• Enforcement: Power management allows the administrator to create power plans which can be applied to collections of computers. These power plans configure Windows power management settings on computers, and different power plans can be configured for peak and non-peak working hours.

• Compliance: After applying power plans to computers in the organization, the administrator can run reports to validate that power settings were correctly applied and to calculate power and carbon footprint savings across collections of computers.

[Beta] System Management in the cloud: Intune

By StijnC at April 23, 2010 11:19
Filed Under: Microsoft, Beta

Microsoft is advancing it’s cloud strategy with a new online offering for PC management and security combined with the best Windows experience called Windows Intune. Windows Intune simplifies how businesses manage and secure PCs using Windows cloud services and Windows 7—making it easier for IT staff to manage and secure PCs from virtually anywhere. In addition to the core cloud service in this offering, we’re also providing access to Windows 7 Enterprise upgrades as well as advanced on-premise management and virtualization tools (Microsoft Desktop Optimization Pack).

intune

Microsoft Takes Desktop Management to the Cloud: Introducing Windows Intune

[Powershell] Quick reference April 2010 update

By StijnC at April 23, 2010 11:18
Filed Under: Powershell, Documentation

Quick reference guide to commonly-used Windows PowerShell commands. For best results, open the file in Microsoft Word, print the contents to legal-sized paper (8 inches by 14 inches), and fold the resulting printout in half, making a four-page booklet.

Powershell Quick reference

[Powershell] Scripting Games 2010 announced!

By StijnC at April 13, 2010 09:27
Filed Under: Community, Powershell, Scripting Games 2010

2010_scriptgames_badge1 The scripting games 2010 will start April 26th!

So head over to http://2010sg.poshcode.org, log in with either your Windows Live ID or OpenID, complete your profile,
and wait for the Games to begin on April 26, 2010.

More information can be found on the Hey Scripting Guy blog.

 

 

 

 

 

 

Technet 2.0 live!

By StijnC at March 04, 2010 00:30
Filed Under: Microsoft, Technet

Just noticed that Technet 2.0 is alive and kicking!

Untitled

[Powershell] export info to Excel

By StijnC at July 30, 2009 02:12
Filed Under: Microsoft, Office, Powershell

There is no cmdlet available to export content directly to Excel. Sure you can use the ‘Export-csv’ cmdlet exporting the object(s) to a comma delimited file and use the generated file as a base.

But nevertheless you can address Excel via the com interface. Powershell facilitates the use of com objects via the ‘new-object’ cmdlet in conjunction with the –-ComObject parameter.

   1: $excel = New-Object -comobject Excel.Application

Once we have our Excel object, we can start adding a workbook and worksheets to the newly created workbook accordingly.

   1: #Add a workbook
   2: $workbooks = $excel.Workbooks.Add()
   3: #Select the Worksheet collection in the workbook (standard default = 3)
   4: $worksheets = $workbooks.Worksheets
   5: #Select the first worksheet
   6: $worksheet = $worksheets.Item(1)

Now that we have an active sheet, we can start adding data. lets get all the running processes and dump the information gathered into the sheet.

   1: #Now collect the data we want to export
   2: $processes = Get-Process
   3: $lastcell = $processes.Count
   4: for ($index = 0; $index -lt $lastcell; $index++) {
   5:     $worksheet.Cells.Item($index+1,1) = $processes[$index].Id
   6:     $worksheet.Cells.Item($index+1,2) = $processes[$index].ProcessName
   7: }

As we are not limited to inserting data, we can easily add some calculations to the sheet as well using the excel functions. 

   1: $cell = $worksheet.Cells.Item(3,3)
   2: $cell.Formula = "=TODAY()"

ExcelPowershell_Formula As we all now, graphs pretty things up and management is fond of them.
So let’s add a simple column chart to the current Workbook to visualize the data.

   1: #Lets select our data range
   2: $range = $worksheet.usedRange
   3: #Now add our charts to the workbook
   4: $workbooks.Charts.Add() | out-null
   5: #and select a chart type
   6: $workbooks.ActiveChart.chartType = [microsoft.office.interop.excel.xlChartType]::xlConeCol
   7: #Set the data source
   8: $workbooks.ActiveChart.SetSourceData($range)

ExcelPowershellChart For more information regarding the Charttypes, see MSDN Excel Charttype Enumeration.
Now lets use a template excel file and dumb the running process data into the predefined range.

   1: #Create the Excel com object
   2: $excel = New-Object -comobject Excel.Application
   3: #Open the workbook
   4: $workbooks = $excel.Workbooks.Open("C:\Users\StijnC\Documents\Test.xlsx")
   5: #get a hold of all the worksheets
   6: $worksheets = $workbooks.Worksheets
   7: #Select the first worksheet
   8: $worksheet = $worksheets.Item(1)
   9: #Now collect the data we want to export
  10: $processes = Get-Process
  11: $lastcell = $processes.Count
  12: for ($index = 0; $index -lt $lastcell; $index++) {
  13:     $worksheet.Cells.Item($index+1,1) = $processes[$index].Id
  14:     $worksheet.Cells.Item($index+1,2) = $processes[$index].ProcessName
  15: }

ExcelPowerShellTemplate

The last action that still remains is saving the excel file and disposing the objects.

   1: #close workbook and dispose the objects
   2: $workbooks.Save()
   3: $excel.Quit()
   4: $dummy = [System.Runtime.InteropServices.Marshal]::ReleaseComObject($worksheet)
   5: $dummy = [System.Runtime.InteropServices.Marshal]::ReleaseComObject($worksheets)
   6: $dummy = [System.Runtime.InteropServices.Marshal]::ReleaseComObject($workbooks)
   7: $dummy = [System.Runtime.InteropServices.Marshal]::ReleaseComObject($excel)

For some reason the Excel process keeps on running.So we kill all excel processes as well.
   1: #if any processes left, kill them
   2: if (ps excel) { kill -name excel}


So its really up to you to define all formatting in a template or create everything from scratch.
Now, this all is quite easy when using USA language settings, try using different settings and all this breaks.powershell regional settings
Even setting the language settings explicit does not solve the problem. You need to define the language settings every time.
The previously defined settings are only valid for the current thread. As Powershell uses a different thread for each command line, this solution is not really feasible.

You could go for a superb function “Using-Culture”, more info can be found on the Powershell Team Blog.
Or we could make sure that all our Excel programming runs in the same thread.
Welcome “script blocks”!

   1: & {
   2: #Create a Culture
   3: $enUS = [System.Globalization.CultureInfo]::CreateSpecificCulture("en-US")
   4: #Set the Current thread Culture to en-US
   5: [System.Threading.Thread]::CurrentThread.CurrentCulture = $enUS
   6: #Create the Excel com object
   7: $excel = New-Object -comobject Excel.Application
   8: #Open the workbook
   9: $workbooks = $excel.Workbooks.Add()
  10: $worksheets = $workbooks.Worksheets
  11: #Select the first worksheet
  12: $worksheet = $worksheets.Item(1)
  13: #Now collect the data we want to export
  14: $processes = Get-Process
  15: $lastcell = $processes.Count
  16: for ($index = 0; $index -lt $lastcell; $index++) {
  17:     $worksheet.Cells.Item($index+1,1) = $processes[$index].ProcessName
  18:     $worksheet.Cells.Item($index+1,2) = $processes[$index].WS
  19: }
  20: #Lets select our data range
  21: $range = $worksheet.usedRange
  22: #Now add our charts to the workbook
  23: $workbooks.Charts.Add() | out-null
  24: #and select a chart type
  25: $workbooks.ActiveChart.chartType = [microsoft.office.interop.excel.xlChartType]::xlConeCol
  26: #Set the data source
  27: $workbooks.ActiveChart.SetSourceData($range)
  28: $workbooks.SaveAs('C:\Users\StijnC\Documents\Process.xlsx')
  29: $excel.Quit()
  30: }

we define the full script as a “script block” and all the magic just works. once we defined the locale.

 

 

 

 

 

 

 

 

 

 

 

 

 

ExcelPowershellFinal

[Powershell] – renaming folders

By StijnC at January 23, 2009 00:19
Filed Under: Powershell

Last day I wanted to have uniform folder names, some of the folders currently have a set of ‘[‘, ‘]’ chars containing dates and some additional info afterwards.
As this was not really necessary and only makes the name longer then needed I decided to rename them, of course using Powershell.
Initially I needed to collect a list of all items:

gci $pwd -recurse

But i was only interested in the folders, so a where clause is in order:

gci $pwd -recurse | where {$_.Mode -match "d"}

Now that we have a list of all folders, we can start with renaming them leaving all chars as from the first ‘[‘:
after a lot of struggling and my one liner not working  I turned to good all friend ‘Google’ and the solution was found on  Mike Ormond's Blog.
Let’s give it another spin:

gci $pwd | where {$_.Mode -match "d"} | move-item -dest { join-path $pwd ([regex]'\[(.*)').replace($_.Name, "")}

nevertheless i got a new error:

Move-Item : The process cannot access the file because it is being used by another process.
At line:1 char:50 gci $pwd | where {$_.Mode -match "d"} | move-item  <<<< -dest { join-path $pwd ([regex]'\[(.*)').replace($_.Name, "")}

but as i looked into my directory, all folders where renamed. so i decided to add the following switch:

-ea SilentlyContinue –ev errorlog

Bare in mind that it is not always wise to let Powershell continue on errors, but as it did the job for me…
the variable $errorlog still holds all errors encountered in the IO operation and can easily be outputted to the console screen or a file.
the PowerShell Team has a great blog entry on 'Managing non-terminating errors' .