DAdams982

Hopefully I get this right. I should first run the how to attatched at the top of this thread, then I can use VAMT to add keys? How difficult is this with a closed network? I know KMS try's to phone home every so often, is the a problem with KMS?

So, writing myself a checklist of what I need for a new internal HA exchange 2010 site. This will not be connected to the internet for mail, but just internal to the organization in a closed area. I have setup and managed DMS (Defense Messaging Service) which was just Exchange 5.5 with some security extensions to it. But it looks like HA has changed in 2010 since back in the day. My site is small, but I will have SAN disk ready for hookup by fiber... so now I am confused on what to get from there. I assume two servers for the CAS and DAGs? Can I run CAS and DAG on one server? Pretty much I am hoping I can buy two servers and expand my SAN.

Your problem sounds like a simple permissions issue. What I understand is the files are being written fine, but people cannot access the files unless being a local admin? Make sure the share perms are populated with who you want, as well as the NTFS perms. Here is something pulled from technet. Creating an NFS shared folder The next step is to use NFS sharing to create an NFS shared folder on the computer running Server for NFS. You can later mount this shared folder on a UNIX client and create a test file on it. To create a shared folder using NFS sharing 1. On the computer running Server for NFS, create a folder to use as the NFS shared folder. 2. Right-click the folder you created and click NFS Sharing. 3. Select Share this folder. 4. If you want to allow anonymous access, select Allow anonymous access. 5. Click Permissions, click Add, and then do either of the following: * In the Names list, click the clients and groups you want to add and click Add. * In the Add Names box, type the names of clients or groups you want to add, separating names in the list with a semicolon (. 6. In the Type of Access list, click the type of access you want to allow the selected clients and groups. 7. Select Allow Root Access if you want a user identified as root to have access other than as an anonymous user. By default, the user identifier (UID) root user is coerced to the anonymous UID. 8. In the Encoding list, click the type of directory name and file name encoding to be used for the selected clients and groups. 9. Click OK twice, and then click Apply. noteNote To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. noteNote To see a list of the members of a group, in the Names list, click a group, and then click Members. Specifying default permissions for new files and folders You can specify the default permissions that will be applied to any file or folder created on an NFS shared resource by the computer running Client for NFS. You can assign Read, Write, and Execute permissions to Owner, Group, and Others. * Owner. The person creating the file. By default, Owner has Read, Write, and Execute permissions. * Group. The primary group of the person creating the file. By default, Group has Read and Execute permissions. * Others. Other file system users (equivalent to Everyone in Windows). By default, Others have Read and Execute permissions. To specify default file permissions 1. On the computer running Client for NFS, open Services for NFS. To open Services for NFS, click Start, point to Administrative Tools, and then click Services for Network File System. 2. In the console tree, right-click Client for NFS and click Properties. 3. On the File Permissions tab, select the default file permissions to apply to each new file and folder created by this computer, and then click OK. noteNote To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority.

I have scoured the net for how to's and checked on here for guides but am not finding what I need. Was hoping some one could point me in the right direction to get started. I have a closed network that is shut off from the rest of the world. I have SCCM 07 R2 and all that jazz, but I need a more automated way to patch my workstations. I know it is quite easy with WSUS, but it is in a closed network so cannot contact the outside. Does anyone have any knowledge in setting up a site like this, I know you can import patches some how from an outside WSUS server, but cannot find anything definitive on how, just that it can be done. Any help would be greatly appreciated.

Thanks for the welcome. I have used many of your screen shot how to's. I have read the microsoft papers on installing SCCM and there is so much crap they left out that one would just not know about without intimate knowledge.

Just stopping in to introduce myself. Finally made an account after using many of the SCCM guides on here. I am a Windows admin for a geospatial imaging company, and only just started to play with SCCM since my closed network is growing pretty quickly. Time to automate many of the processes. Looking forward to sharing what knowledge I have, and learning what you all know. I am a MCSE 2003: Security, and a MCTS 2008 (All three designators)