Windows 8.1Senior Product Marketing Manager at Microsoft Ben Hunter recently blogged about a new way that Windows 8.1 can be installed while still ensuring that there is plenty of storage left for apps and data.

The method uses the well-known Windows Image Boot format. But instead of uncompressing the image during installation, WIMBoot keeps all of the operating system files compressed on a separate partition. From the user’s perspective, however, nothing looks any different: You still see a C: volume containing Windows, your apps, and all of your data.

A standard WIM file is not usually bigger than around 3GB. This allows for installation on devices with smaller disks, e.g. devices with 16GB or 32GB SSDs or eMMC storage, while still ensuring that there is plenty of storage left for apps and data.

Note that UEFI is a requirement and that WIMBoot will only be supported on Windows 8 logo-certified devices.

Read more about Windows Image File Boot (WIMBoot) here.
http://technet.microsoft.com/en-us/library/dn594399.aspx

Read about Michael Niehaus experiences from experimenting with WIMBoot using MDT 2013 here:
http://blogs.technet.com/b/mniehaus/archive/2014/04/13/experimenting-with-wimboot-using-mdt-2013.aspx

Hi!

I got some problem when I tried to install Windows Server Update Services on my Test Windows Server 2012 Sp1 with SQL Server 2012 Sp1 installed. The Role installation worked fine. When after a post-installation runs it fails. After some research, I notice the post-installation didn’t found the wsusutil.exe tool (Wsus post-installation use this tool to do a post-installation). I’d a simple file search on server, and found the tool under c:\Program Files\Update Services\Tools. Run it from a powershell console:

 If you have install Wsus and choosed Database, run this command:

wsusutil.exe postinstall CONTENT_DIR="WSUS-CONTENT-PATH" SQL_INSTANCE_NAME="SQL-SERVER-NAME"


Skärmavbild 2013-09-04 kl. 11.20.08

If you have install Wsus and choosed WID database, run this command:

wsusutil.exe postinstall CONTENT_DIR=C:\WSUS INSTANCE_NAME="computername\database_instance_name"

jobba-hemmaSvårt att ta sig till jobbet? –  Jobba hemma!

Med anledning av president Obamas Sverigebesök förväntas stora störningar i trafiken. Vi hoppas att alla som kan och har möjlighet att jobba hemma gör det.

Microsoft ger HÄR fem bra tips som gör det lättare att jobba hemma.

Dessutom så har de väldigt bra verktyg och lösningar som gör det ännu enklare så som t.ex. Remote Access och Office 365 för att bara nämna några.

 

WindowsMicrosoft avslöjar nu på sin blogg en stor del av innehållet i den kommande uppdateringen av Windows 8.
Startknappen från Windows 7, som många har frågat efter, kommer inte tillbaks.
Istället lanseras en ny sorts startknapp. Den kommer finnas i det nedre vänstra hörnet och kommer när du klickar på den visa en lista med alla installeradde appar.

Iom Windows 8.1 kommer man också kunna ställa in så att Windows startar direkt till skrivbordet.

Dessutom presenteras utökningar/förändringar och förbättringar av bl.a.
– Personlig anpassning (Personalization)
– Sök
– Inbyggda appar och Windows Store
– Koppling till molnet (SkyDrive)
– Inställningar (blir lättare att komma åt)
– Internet Explorer 11
– Mus och tangentbordsinställningar

Läs mer på Microsofts blogg:
http://blogs.windows.com/windows/b/bloggingwindows/archive/2013/05/30/continuing-the-windows-8-vision-with-windows-8-1.aspx

WindowsDet har under en tid ryktats om en ”ny” version av Windows 8, ett projekt som har gått under arbetsnamnet Windows Blue.

Nu bekräftar Microsoft att det snart kommer en ny version som kommer heta 8.1 samt att den kommer vara gratis för användare av Windows 8. Vidare skriver de att den kommer finnas som sk. public preview (både för Windows 8 och Windows RT) med start den 26 juni.

Läs mer på Microsofts Windows-blogg:
http://blogs.windows.com/windows/b/bloggingwindows/archive/2013/05/14/windows-keeps-getting-better.aspx

During SQL 2012 SP1 installation on a Windows 2012 Server i got the following Error.

sql_error

The installation finished with some error.

sql_error2

To fix this, first I need to install .Net Framwork 3.5 and then mount my windows 2012 media as D:\ and run the follwoing command as administrator.

Dism /online /enable-feature /featurename:NetFx3 /All /Source:D:\sources\sxs

sql_error3

I rerun the SQL setup and successfully installed it.

sql_error4

Here comes some instructions, howto Enable Powershell Remoting in a Windows Domain.

Step 1 – Set Powershell Execute Policy:

By Default the powershell allow only code-signed powershell script. To be able to change this settings to RemoteSigned (Enable Local scripts to run without to be signed. Scripts that is downloaded from the internet, must be signed.) you can do following:

  1. Create an new GPO ex: Set Computer Settings – Enable Powershell Remoting
  2. Right-click on new gpo and choose Edit
  3. Expand and goto ”Computer Configuration > Polices > Administrative Templates > Windows Components > Windows PowerShell
  4. Right-Click on Setting: Turn On Script Execution and choose Edit
  5. Turn on Policy setting, click on Radio-option Enable
  6. On Select Menu Execution Policy, Choose Allow local scripts and remote signed scripts
  7. Click Button OK

Step 2 – Allow remote Server Management through WinRM:

Enabling Powershell Remoting on every servers and clients in your environment you can do it from group policy.

  1. Right-Click on same GPO you just created Set Computer Settings – Enable Powershell Remoting and choose Edit
  2. Expand and goto ”Computer Configuration > Polices > Administrative Templates > Windows Components > Windows Remote Management (WinRM) > WinRM Service
  3. Right-Click on Setting: Allow remote server managment through WinRM and choose Edit
  4. Turn on Policy setting, click on Radio-option Enable
  5. On Options :
    1. IPv4 filter: * or specific ip-adress scope the service will be enable for
    2. IPv6 filter: * or specific ip-adress scope the service will be enable for
  6. Click Button OK

Step 3 – Turn on Service Windows Remote Management (WS-Management):

By Default Service ”Windows Remote Managment” is not turned on.  To turn on to every server and clients you have in your the windows environment, you can do it by a group policy.

  1. Right-Click on same GPO you just created Set Computer Settings – Enable Powershell Remoting and choose Edit
  2. Expand and goto ”Computer Configuration > Polices > Windows Settings > Security Settings > System Services
  3. Right-Click on Setting: Windows Remote Management (WS-Management) and choose Properties
  4. Click option and Select:  Define this policy setting
  5. Select Radio-option: Automatic
  6. Click Button OK

Step 4: Allow Windows Remote Managment through Windows Firewall:

Do this step If you have Windows Firewall Group Policy:

  1. Create an new GPO ex: Set Computer Settings – Configure Firewall
  2. Right-click on new gpo and choose Edit
  3. Expand and goto ”Computer Configuration > Polices > Windows Settings > Security Settings > Windows Firewall > Windows Firewall
  4. Right-Click on setting: Inbound Rules and choose New Rule
  5. Select Radio-Option: Predefined
  6. Choose in Select Menu: Windows Remote Managment (HTTP-In)
  7. Click Next until End of wizard.
  8. Right-click on the new Rule: Windows Remote Managment (HTTP-In)  and choose Properties
  9. Goto Tab:  Advanced and uncheck option Public.
  10. Goto Tab: Scope and add select radio-option These Ip adresses: Under Remote IP adress.
  11. Click on Add button
  12. Select Radio-Option: This IP adresses range
  13. In From Input option: ex: 192.168.1.100
  14. In To Input option: ex: 192.168.1.254
  15. Click on Button OK
  16. Click on Button Apply and then OK

Step 5 – Do a Group Policy Update:

  1. Start command prompt in admin context, and type following: Gpoupdate /force
  2. Press Enter.
  3. Or wait to next restart of your clients and servers.