Foutmelding bij installeren webapps Office365

Op kantoor hebben wij Office365 in gebruik. Voor onze afdeling willen wij ook gebruik gaan maken van de webapps zoals Microsoft Project. Nadat de licentie geactiveerd was probeerde ik de software “geïnstalleerd” te krijgen. Ik heb lokaal Office 2013 Pro Plus 64 bits geïnstalleerd staan. Dus de webapps moeten ook 64 bits zijn/worden. De foutmelding die ik kreeg is “We’re sorry office (32-bit) couldn’t be installed”.

Foutmelding installatie Microsoft Project

Foutmelding installatie Microsoft Project

Door op de link “Go online for additional help” te klikken kwam ik niet bij de informatie die ik nodig had. Wel kreeg ik de info door te zoeken met Google. Ik kwam deze link tegen. In deze lijst stond de melding “Why can’t I install both the 32-bit and 64-bit versions of Office 2013?“. Helemaal onderaan staat de oplossing bij “During setup, From my account”.

In het kort:

1) Log in via OWA

2) Klik rechtsboven (als je IE gebruikt) op het radertje naast vraagteken

3) Klik op Instellingen voor Office365

4) Klik links in ‘menu’  op software

5) Wijzig in het middengedeelte Language en version

6) klik op install

7) Mogelijk krijg je een beveiligingsmelding

8) Klik op run en volg de instructies die je krijgt

Tip! Voor het complete pakket moet het systeem nog aangevuld worden met enkele files die gedownload moeten worden. Dit gebeurd in de achtergrond. Je krijgt ook waarschuwingen daarover. De installatie moet compleet zijn voordat de laptop/computer/device afgesloten kan/mag worden.

 

 

Microsoft Network Monitor 3.4 DNS source destination

Filtering in results of the Microsoft Network Monitor isn’t easy. But with the following handy steps you can solve this problem very quickly. Open your DHCP server and export the list of Address Leases (see screendump).

dhcp

 

 

 

 

 

 

 

Open the result in Microsoft Excel. Copy the first 2 columns and past this in a new Excel document and save as .TXT. Browse to the My Documents folder. Open the folder “Network Monitor 3” and subfolder “Aliases”. Open the *.NMA with notepad. Open the .TXT mentioned above. Copy the content in the opened *.NMA. Copy the spaces between the ip-address and the DNS-name. Replace this with one space. Save the documents and you are ready.

Mount and unmount wim-file

How use DISM for mounting a wim-file? With the following example I will show you how to do:

  • The name of the wim-file is LTI_WIN7_64.wim
  • The test location is C:\Test
  • the location of the wim-file is: D:\RemoteInstall\Boot\x64\Images
  1. Open een elevated prompt.
  2. Go with the following command to the directory mentioned earlier cd “D:\RemoteInstall\Boot\x64\Images” [enter]
  3. dism /mount-wim /wimfile:LTI_WIN7_64.wim /index:1 /mountdir:”C:\Test”
  4. Go by Explorer to C:\Test. You can also see the content of the wim-file

How use DISM for mounting a wim-file? With the following example I will show you how to do:

  1. Close all browser sessions to the mount-location
  2. Open een elevated prompt.
  3. Go with the following command to the directory mentioned earlier cd “D:\RemoteInstall\Boot\x64\Images” [enter]
  4. dism /unmount-wim  /mountdir:”C:\Test” /discard

 

 

SCCM Client Agent TAB Actions explanation

I found today a very interesting article in which al possible actions of the SCCM Client Agent TAB Actions is explained. Look here fore the original article. Below you will find a shortage of that page:

  • Branch Distribution Point Maintenance Task verifies any prestaged packages and downloads any that do not exist on the branch distribution point. While Technet does not explicitly state it, I believe this task is useful only on branch distribution points and is ignored on normal clients.
  • Discovery Data Collection Cycle causes the client to generate a new discovery data record (DDR). When the DDR is processed by the site server, Discovery Data Manager adds or updates resource information from the DDR in the site database.
  • File Collection Cycle When a file is specified for collection, the Microsoft System Center Configuration Manager 2007 software inventory agent searches for that file when it runs a software inventory scan on each client in the site. If the software inventory client agent finds a file that should be collected, the file is attached to the inventory file and sent to the site server. This action differs from software inventory in that it actually sends the file to the site server, so that it can be later viewed using Resource Explorer. This is a part of SCCM inventory functionality.
  • Hardware Inventory Cycle collects information such as available disk space, processor type, and operating system about each computer. This is a part of SCCM inventory functionality.
  • Machine Policy Retrieval & Evaluation Cycle The client downloads its policy on a schedule. By default, this value is configured to every 60 minutes and is configured with the option Policy polling interval (minutes). However, there might be occasions when you want to initiate ad-hoc policy retrieval from the client—for example, in a troubleshooting scenario or when testing. This action initiates ad-hoc machine policy retrieval from the client outside its scheduled polling interval.
  • Software Inventory Cycle collects software inventory data directly from files (such as .exe files) by inventorying the file header information. Configuration Manager 2007 can also inventory unknown files — files that do not have detailed information in their file headers. This provides a flexible, easy-to-maintain software inventory method. You can also have Configuration Manager 2007 collect copies of files that you specify. Software inventory and collected file information for a client can be viewed using Resource Explorer. This is a part of SCCM inventory functionality.
  • Software Metering Usage Report Cycle collects the data that allows you to monitor and client software usage.
  • Software Updates Deployment Evaluation Cycle initiates a scan for software updates compliance. Before client computers can scan for software update compliance, the software updates environment must be configured.
  • Software Updates Scan Cycle Just after a software update installation completes, a scan is initiated to verify that the update is no longer required and to create a new state message that indicates the update has been installed. When the installation has finished but a restart is necessary, the state will indicate that the client computer is pending a restart.
  • User Policy Retrieval & Evaluation Cycle Similar to Machine Policy Retrieval & Evaluation Cycle, but this action initiates ad-hoc user policy retrieval from the client outside its scheduled polling interval.
  • Windows Installer Source List Update Cycle causes the Product Source Update Manager to complete a full update cycle. When you install an application using Windows Installer, those Windows Installer applications try to return to the path they were installed from when they need to install new components, repair the application, or update the application. This location is called the Windows Installer source location. Windows Installer Source Location Manager can automatically search Configuration Manager 2007 distribution points for the source files, even if the application was not originally installed from a distribution point.