1. Create the Office 365 click-to-run package for local deployment.
- Download the Office Deployment Tool http://www.microsoft.com/en-us/download/details.aspx?id=36778 and extract this download to a folder.
- Edit from the extracted folder the configuration.xml file
- configuration.xml syntax can be found at https://technet.microsoft.com/en-us/library/jj219426(v=office.15).
<Add SourcePath=”D:\Office\O365ClickToRun\Download” OfficeClientEdition=”32″ >
<Language ID=”en-us” />
<!– <Updates Enabled=”TRUE” UpdatePath=”\\Server\Share\Office\” /> –>
<Display Level=”None” AcceptEULA=”TRUE” />
<Logging Name=”OfficeSetup.txt” Path=”%temp%” />
<Property Name=”AUTOACTIVATE” Value=”1″ />
- Run from an elevated CMD prompt :
- setup /download configuration.xml
- This wil download all of the click-to-run components to the specified folder.
- When the download is finished there will be a number of cabinet files in the folder
- It’s easy to create an App-V 5 package which can be deployed using System Center Configuration Manager 2012
To create thsi App-V package run the following command :
- setup /packager configuration.xml s:\office\O365clicktorun\Appv5
- Now the App-V 5 package will be created in the specified folder.
This package can be used by your SCCM server
If there are any issues or erros deploying this package via SCCM you can check this : http://mieffel.noonkief.nl/?p=853
The Skype for business client crashes when using a Logitech C920.
1. update Logitech drivers
2. uninstall Citrix receiver
3. Skype for business now works
After this I installed the latest version of the Citrix receiver.
For testing or develop purposes you can get a 2 user 1 year developmen
Go to www.citrix
logon using your username and password. If you don’t have one, create a new user.
Under My Account / Previews/Betas – License Retrieval.
Then under Citrix XenApp Developer Edition – choose retrieve more Licenses
From the resulting page click on the license key and continue with license server allocation
During VMware vCenter 5.1 SSO install I got this error “Database connection has failed”.
Start “Microsoft SQL Server 2008 R2 > Configuration tools > SQL Configuration Manager” and should configure to set TCP Port property to 1433
#Create a NIC team on a single NIC :
New-NetLbfoTeam -Name “SingleNICTeam” -TeamMembers “Ethernet 2″
#Create a NIC team with two NICs
New-NetLbfoTeam -Name “DoubleNICTeam” -TeamMembers “Ethernet 2″, “Ethernet 3″
# Create vNICs on team
Add-NetLbfoTeamNic -Team “SingleNICTeam” -VlanID 15 -Name “VLAN15″
Add-NetLbfoTeamNic -Team “SingleNICTeam” -VlanID 16 -Name “VLAN16″
Start a command prompt
run the command
certutil -config – -ping
Ofice 365: Role Based Access for Administrators #office365
Within BPOS you are either an administrator or you are not. If you are an administrator you are able to administer the entire BPOS environment.
Next to this customers can grant partners administrative access to their environment allowing them to perform all sorts of services.
Office 365 will introduce Role Based Access. This allows several roles to be created within an organization:
|Tenant Admin||Includes full permissions to your company. The initial user created when signing up will be assigned this role. Can assign admin permissions to other users.|
|Billing Admin||Has full permissions for billing tasks, and read only permissions for company objects (domains, users). Any user with this role will also receive notifications for billing events.|
|User Account Admin||Has read only permissions to all company objects, and has user administration permissions. Cannot make changes to billing or tenant admins.|
|Help Desk Admin||Has read only permission to all company objects, and has reset password privileges. Cannot reset password for tenant, billing or user account admins.|
|Service Support Admin||Has read only permissions to all company objects. Also has the ability to manage individual services.|
|User||This is the default role for all users, and does not include any admin permissions.|
Next to this partners can be given access to the environment allowing them to perform all sorts of maintenance and support tasks. Two roles will be available for partners:
|Agent Admin||Agent will have full access (Tenant Admin role) on all tenants that the partner has access to.|
|Agent Help Desk Admin||Agent will have access to reset passwords only (Help Desk Admin role) on all tenants that the partner has access to.|
- Download the Windows Software Development Kit (SDK) for windows 8 from the microsoft site.
- Install the Windows Performance Toolkit for your OS version (32 or 64 bits).
- If you have a 64bit installation of Windows, you will need to modify the registry to enable full tracing to work properly.
Open regedit, browse to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management, double-click the “DisablePagingExecutive” value, and change it from “0” to “1”. Click “OK”
- Open an elevated command prompt
- to generate a boot trace, you will need to type the following :xbootmgr –trace boot -traceFlags LATENCY+DISPATCHER+DISK_IO_INIT+NETWORKTRACE+MEMINFO+POWER+PERF_COUNTER+PRIORITY+REGISTRY+FILE_IO+FILE_IO_INIT -postBootDelay 300 -stackWalk Profile+ProcessCreate+CSwitch+ReadyThread+Mark+ThreadCreate+DiskReadInit+DiskWriteInit+DiskFlushInit+RegSetValue+RegCreateKey+RegSetInformation -resultPath C:\Boot_Trace
- This command will cause your machine to shut down and reboot automatically. Once the system restarts, please log back in as soon as possible to minimize the size of the resulting trace file. Once logged in, the system will present a dialog box letting you know that it is waiting 120 seconds (it will count down) before finishing the trace. DO NOT use your computer to do anything during this time.
- Once the trace is complete, you will find a large .ETL file and a log file in C:\Boot_Trace.
Create a new shortcut to “%systemroot%\system32\Snipping Tool.exe”
In an elevated command prompt you can check with this command which device caused the last awake of the system.
to find hardware devices that can wake your computer, run the following command:
powercfg -devicequery wake_armed
You can change this settings via device manager,
Properties of the device.Choose the powermanagement tab and uncheck
Allow this device to wake the computer check box and click OK
Also check the scheduled tasks that are allowed to wake you computer
You can edit this scheduled task in the Windows task scheduler.