March 2009 - Posts
Morning,
Problem I have been working on for the last few weeks, was running the print command from the command prompt to a 2008 hosted printer...You receive and error of "Unable to Iniatialize Device "
This problem only occurs when the printer is physically hosted on a 2008 Server
Microsoft have confirmed that this problem is due to smb2 which is new with Server 2008 and Vista, they are also currently working on a patch for the problem. There is however 2 options for getting this to work
1. Host the printer on a 2003 Server
2. Disable SMB2 and revert back to SMB1 - See this guide for Details, Again, Thank you to the Petri Website for this guide which once again has proven amazingly accurate and indepth. Whilst it doesnt specifically mention print.exe, Microsoft have vocalised the problem and I have tested this solution with success
http://www.petri.co.il/how-to-disable-smb-2-on-windows-vista-or-server-2008.htm
James
2008 Has introduced one of the most interesting AD problems I have come across....Unfortunately for me, this problem has shown its face in my production environment so things are a little more tricky when trouble shooting. Some Background 2008 Server...
When playing with the OS Deployment tools in SCCM, we discover yet another wonderful option in the Task Sequences that allow us to automatically join a machine to a domain after the SYSPREP process runs - unreal!
A few tips when setting this up before creating your task sequence media and imaging your machines. This option is found under the network settings option in your task sequence...
1. Create an account in AD specifically for this domain join portion of the sequence. If you control who can join the domain via groups and group policy, then add this user to the required group. If not, then you can use the delegation of control wizard to allow permissions for Domain Join Only on this account
2. In the actual Task sequence option, Do not specify the default computers container in Active Directory for your machine locations....(this is a redundant point if your SCCM Server is a DC). Create a dedicated OU on the root of your Domain for Client Machine locations eg: LDAP://OU=SCCM Computer Joins,DC=Domain,DC=Local If you do not specify a specific OU, It will fail the join
3. Specify your Domain Joining account in the account options under Network settings.
Once you have OS deployment happening, SCCM's ability to continue your usual manual tasks automatically is unreal
James
One of the bugs that I have come across so far with config manager, is the client installation push for the SMS agent....Whilst the collections will poll Active Directory and update thelmselves with machines, right clicking either a collection, or an actual client machine and selecting "install agent", leaves you wondering where your agent is - 24 hours later!....The same can be said when trying to manually install the client agent on a client machine or server....
After trauling and trauling, reinstalls from scratch using two different environments, I discovered this blog which resolved our issues.
http://social.technet.microsoft.com/forums/en-US/configmgrsetup/thread/24029fc2-6898-4d99-81cf-301c339f9784/
Seems that this fix so far is not officially documented by MS, but I can imagine there are a stack of people who are running into this problem on a 64 bit Windows Server 2008 Platform, Hope this can help you out in your environments
The Client install log (located in the System Centre Install Folder) will display the following
___________________________________________________________________________
From the client's CCMSetup.log
Failed to correctly recieve a WEBDAV request
Failed to successfully complete HTTP request (StatusCode at WinHttpQueryHeaders: 405)
Sending Fallback Status Point message, STATEID='301'
___________________________________________________________________________
The Solution....
___________________________________________________________________________
%windir%\System32\inetsrv\config\applicationHost.config
1. Open the applicationHost.config file to edit it.
2. Search for "Handlers accesspolicy"
3. Paste the following information on the next line
<add name="WebDAV" path="*" verb="PROPFIND,PROPPATCH,MKCOL,PUT,COPY,DELETE,MOVE,LOCK,UNLOCK" modules="WebDAVModule" resourceType="Unspecified" requireAccess="None" />
_____________________________________________________________________________________
Good luck
J
So! Some happier news on from my last not so positive post....System Centre is certainly starting to kick some serious ass....
I have just push Configuration Manager 2007 (SCCM) and Operations Manager 2007 (SCOM) Live and wow....what a system!! I am absolutely dumbfounded by how far along these programs have come, and loving every minute of it!
These tools, in particular, Configuration Manager are absolutely amazing for your client and server management needs - and are making my deployment of over 100 sites looking a far less daunting task....
I would deffinitely reccomend both of these products to anyone, but would also advise a test environment first to iron out the bugs, of which there are a few that i will post about a little later on....
On a whole, a way way better experience than that of Hyper V! Will post some advice and querks to help out along the way when I get some more time
J