Windows 8 - Detailed preview

Microsoft showcased a detailed preview of the next major release of Windows

 Touch-First User Interface

• Metro style. Windows 8 introduces a new Metro style interface built for touch, which shows information important to you, embodies simplicity and gives you control. The Metro style UI is equally at home with a mouse and keyboard as well.

• Touch-first browsing, not just browsing on a touch device. Providing a fast and fluid touch-browsing experience, Internet Explorer 10 puts sites at the center on new Windows 8 devices.

More Ways to Engage With Powerful, Connected Apps

• Powered by apps. Metro style apps built for Windows 8 are the focal point of your experience, filling your entire screen so there are no distractions.

• Apps can work together. Apps communicate with each other in Windows 8. For example, you can easily select and email photos from different places, such as Facebook, Flickr or on your hard drive.

• Your experience syncs across your devices. Live roams all the content from the cloud services you use most — photos, email, calendar and contacts — keeping them up-to-date on your devices. With SkyDrive, you can access your files, photos and documents from virtually anywhere with any browser or with Metro style apps in Windows 8.

Enhanced Fundamentals

• The best of Windows 7, only better. Windows 8 is built on the rock-solid foundation of Windows 7, delivering improvements in performance, security, privacy and system reliability. Windows 8 reduces the memory footprint needed — even on the lowest-end hardware — leaving more room for your apps.

• Preserving power-user favorites and making them better. For those who push the limits of their PC, Windows 8 features an enhanced Task Manager and Windows Explorer and new, flexible options for multimonitor setups.

Duplicate Records When You Use Unknown Computer Support with Active Directory Delta-Discovery

Known Issue and Workaround: You might see duplicate records when you use unknown computer support with Active Directory Delta-Discovery in Configuration Manager 2007 R3.

Read more:
http://blogs.technet.com/b/configmgrteam/archive/2011/09/09/known-issue-and-workaround-duplicate-records-when-you-use-unknown-computer-support-with-active-directory-delta-discovery.aspx

Configuration Manger 2007 PXE & DHCP on the same server (Quick Guide)

1.       Make sure that the server do not have PXE installed

a.       Remove all bootimage images from the affected PXE server Distribution Point

b.      From the console, remove the PXE service role.

c.       Check the Program Files\Microsoft Configuration Manager\Logs\PXEsetup.log to verify that the role is removed successfully.

d.      Remove the Windows Deployment Service.

e.      Reboot the Configuration Manager site server, if WDS was installed on the site server.

2.       Install WDS but do not configure it.

3.       Assuming DHCP and WDS are installed on the same Configuration Manager server,

a.       Make sure that DHCP Option 60 is set

                                                               i.      NETSH

                                                             ii.      NETHSH>DHCP server \\nameofserver

                                                            iii.      add optiondef 60 PXEClient String 0 comment=”Option added for PXE Support”

                                                           iv.      set optionvalue 60 STRING PXEClient

                                                             v.      show optionvalue all

                                                           vi.      exit

b.      Enabled and choose don’t listen on port 67.

                                                               i.      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE

                                                             ii.      Set the UseDHCPPorts registry value to 0

4.       Install the PXE service role from the console

5.       Check the PXEsetup.log to verify that the role was installed successfully.

6.       Update the PXE distribution points for the boot images now that the new role is installed.

7.       The target client should now be able to PXE boot to the Configuration Manager server.