There is a very well known “trick” to hide shares with Windows and that is to put a $ sign at the end of the share name. The problem is that this doesn’t work if you are using DFS Namespaces (DFSN). The reason why it doesn’t work is because DFSN doesn’t advertise shares – it advertises folders and there is an underlying mechanism to transparently redirect computers trying to connect to those folders to the underpinning shares. So if you have folders in your DFS Namespace that you want to hide just as if they were a share, how do you do it? The answer lies in the fact that they are, indeed, folders. Go to the DFSN root server and open up the folder for your namespace. Right-click on the folder you want to hide and choose Properties. Then select the Hidden attribute and click OK. You will be asked if you want to apply the change to this folder only or to this folder, subfolders and files. You only need to apply the change to this folder only. Be mindful of the fact, though, that this trick of hiding the folders only works so long as users aren’t showing hidden files and folders on their computers. If they are, these folders will still show up. To make it even harder for users to find these “hidden” folders, it is necessary to set the System attribute on the folder. This then prevents the folders from being seen unless the user has unticked “Hide protected operating system files”. Setting the system attribute on a folder requires the use of the attrib command with a very specific sequence of flags: attrib –r +h +s <folder path> The –r flag removes the read-only setting which is normally used by Windows on folders as an indicator that the folder might have customisation on it. Since we are talking about folders in the DFS Namespace, that isn’t going to apply here. The +h flag applies the hidden setting. You need to do this as part of the same command as +s in order to make sure that the folder does actually get hidden and not just set as a system folder. You cannot apply the hidden flag after the folder has got the system flag set. The +s flag applies the system setting. Bron
QNAP - Headphones Updating:
/etc/init.d/Headphones.sh stop cd /share/MD0_DATA/.qpkg/Headphones/ mv headphones/__init__.py headphones/__init__.py.bak git remote set-url origin git://github.com/rembo10/headphones.git git pull git checkout master /etc/init.d/Headphones.sh start rm -rf headphones/__init__.py.bak
How to place FSMO and Global Catalog roles in Active Directory During installation of Active Directory on a Windows Server 2000/2003/2008 all FSMO roles will automatically be installed on the first server. But Best Practice dictates to move some of theese Flexible Single Master of Operation (FSMO) roles to seperate servers. If you only have one domain controller (not recommended), there is nothing to do since all roles must be on this server, but if you have multiple servers you should move some of theese roles on to more servers. It is also important to be aware of what servers are Global Catalog servers, especially if you have more than one domain and even if only one domain, they will be prefered by applications like Exchange server. It is recommended to place the forest roles on one Domain Controller (DC) and the domain roles on another server. If not all Domain Controllers are Global Catalog servers, it is also important to place the infrastructure master on a server that is NOT a Global Catalog server. Recommended Best Practice setup of FSMO roles. Domain Controller #1 Place the two forest roles on this server.
Getting Ready # Install Windows 7 from scratch on to your test machine. DO NOT upgrade from Windows XP, this needs to be a fresh install. Customise Windows 7 with any software, security settings or general settings you wish. When you install from this image all the settings as well as user accounts will be installed by default. Install WAIK for 7/2008 on the test PC. Download from here (1.7GB). Create WINPE Disk # Right click command prompt run as admin Change to directory “C:Program FilesWindows AIKToolsPETools” run command “copype x86 c:winpe” run command “imagex /mountrw c:winpewinpe.wim 1 c:winpemount” copy imagex.exe from “C:Program FilesWindows AIKToolsx86imagex.exe” to “c:winpemountwindowssystem32″ Create wimscript.ini in “c:winpemountwindowssystem32″ with following inside [ExclusionList] ntfs.log hiberfil.sys pagefile.sys "System Volume Information" RECYCLER WindowsCSC [CompressionExclusionList] *.mp3 *.zip *.cab WINDOWSinf*.pnf Run Command “imagex.exe /unmount /commit c:winpemount” Run Command “copy c:winpewinpe.wim c:winpeisosourcesboot.wim /y” Run Command “oscdimg -n -h -bc:winpeetfsboot.com c:winpeiso c:winpewinpe.iso” This will create an ISO in c:winpewinpe.iso. Burn this and keep. Now we need to sysprep our machine. (You can remove WAIK and any files you don’t need, test your iso first!) Sysprep Your Machine
ReceiverInstall.exe /addlocal=“ICA_Client,ReceiverInside,SSON,Flash,USB,DesktopViewer,HDX,Vd3d”
Best Practices for Oversubscription of CPU, Memory and Storage in vSphere Virtual Environments Pros and cons of oversubscription and how far it should be taken before it becomes dangerous Scott D. Lowe http://www.vkernel.com/files/docs/white-papers/vsphere-oversubscription-best-practices.pdf vSphere Oversubscription Best Practices
Windows Crash Dump analysis is a fairly expansive topic that ranges from simple post mortem analysis of small memory dump files to remote debugging of a live system and probing the failure as it occurs in the operating system. This series of posts will cover analysis and troubleshooting of many common failures faced by end users on Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, and Windows 8. This specific post examines memory dumps, how to install/use the tools to analyze them, crashes that appear when KeBugCheckEx is called, and initial steps with most dumps. The blue screen of death in Windows 7 and earlier versions of Windows: “A problem has been detected and Windows has been shut down to prevent damage to your computer.” The blue screen of death in Windows 8 Developer Preview: “Your PC ran into a problem that it couldn’t handle, and now it needs to restart. You can search for the error online: %s.”